Package org.docx4j.convert.out.XSLFO
Class XSLFOExporterNonXSLT
java.lang.Object
org.docx4j.convert.out.XSLFO.XSLFOExporterNonXSLT
Deprecated.
Running Xalan extension functions on Android is problematic:
http://stackoverflow.com/questions/10579339/is-it-possible-to-call-a-java-extension-function-from-xalan-on-android
and generating the XSL FO via Xalan + extension functions
is a bit slow,
so this uses TraversalUtils to generate XSL FO output
without any need for Xalan or XSLT.
The intent is that this mechanism will ultimately
completely replace the Xalan based approach, at which
point docx4j will no longer be dependent on Xalan
(the XSLT included in Oracle's java is sufficient for
our mc pre processor)
We could use a simple JAXB model of XSL FO,
or org.w3c.dom to construct the XSL FO document.
This implementation uses org.w3c.dom, since
that is easiest based on existing code.
This class might be neater if it used CompoundTraversalUtilVisitorCallback,
but it would be less obvious what is going on.
- Author:
- jharrop
-
Field Summary
Fields -
Constructor Summary
ConstructorsConstructorDescriptionXSLFOExporterNonXSLT(WordprocessingMLPackage wmlPackage, FOSettings pdfSettings) Deprecated. -
Method Summary
Modifier and TypeMethodDescriptionexport()Deprecated.Generate XSL FO for the entire MainDocumentPart.voidoutput(Document xslfo, OutputStream os, org.apache.fop.configuration.Configuration fopConfigZZZ) Deprecated.
-
Field Details
-
DEFAULT_OUTPUT_SIZE
protected static final int DEFAULT_OUTPUT_SIZEDeprecated.- See Also:
-
-
Constructor Details
-
XSLFOExporterNonXSLT
public XSLFOExporterNonXSLT(WordprocessingMLPackage wmlPackage, FOSettings pdfSettings) throws Docx4JException Deprecated.- Throws:
Docx4JException
-
-
Method Details
-
export
Deprecated.Generate XSL FO for the entire MainDocumentPart.- Returns:
- Throws:
Docx4JException
-
output
public void output(Document xslfo, OutputStream os, org.apache.fop.configuration.Configuration fopConfigZZZ) throws Docx4JException Deprecated.- Throws:
Docx4JException
-