You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

embedding.xml 32KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681
  1. <?xml version="1.0" standalone="no"?>
  2. <!--
  3. Copyright 1999-2006 The Apache Software Foundation
  4. Licensed under the Apache License, Version 2.0 (the "License");
  5. you may not use this file except in compliance with the License.
  6. You may obtain a copy of the License at
  7. http://www.apache.org/licenses/LICENSE-2.0
  8. Unless required by applicable law or agreed to in writing, software
  9. distributed under the License is distributed on an "AS IS" BASIS,
  10. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  11. See the License for the specific language governing permissions and
  12. limitations under the License.
  13. -->
  14. <!-- $Id$ -->
  15. <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
  16. <!-- Embedding FOP -->
  17. <document>
  18. <header>
  19. <title>Apache FOP: Embedding</title>
  20. <subtitle>How to Embed FOP in a Java application</subtitle>
  21. <version>$Revision$</version>
  22. </header>
  23. <body>
  24. <section id="overview">
  25. <title>Overview</title>
  26. <p>
  27. Review <a href="running.html">Running FOP</a> for important information that applies
  28. to embedded applications as well as command-line use, such as options and performance.
  29. </p>
  30. <p>
  31. To embed Apache FOP in your application, first create a new
  32. org.apache.fop.apps.FopFactory instance. This object can be used to launch multiple
  33. rendering runs. For each run, create a new org.apache.fop.apps.Fop instance through
  34. one of the factory methods of FopFactory. In the method call you specify which output
  35. format (i.e. Renderer) to use and, if the selected renderer requires an OutputStream,
  36. which OutputStream to use for the results of the rendering. You can customize FOP's
  37. behaviour in a rendering run by supplying your own FOUserAgent instance. The
  38. FOUserAgent can, for example, be used to set your own Renderer instance (details
  39. below). Finally, you retrieve a SAX DefaultHandler instance from the Fop object and
  40. use that as the SAXResult of your transformation.
  41. </p>
  42. <note>
  43. We recently changed FOP's outer API to what we consider the final API. This might require
  44. some changes in your application. The main reasons for these changes were performance
  45. improvements due to better reuse of reusable objects and reduced use of static variables
  46. for added flexibility in complex environments.
  47. </note>
  48. </section>
  49. <section id="basics">
  50. <title>Basic Usage Pattern</title>
  51. <p>
  52. Apache FOP relies heavily on JAXP. It uses SAX events exclusively to receive the XSL-FO
  53. input document. It is therefore a good idea that you know a few things about JAXP (which
  54. is a good skill anyway). Let's look at the basic usage pattern for FOP...
  55. </p>
  56. <p>Here is the basic pattern to render an XSL-FO file to PDF:
  57. </p>
  58. <source><![CDATA[
  59. import org.apache.fop.apps.FopFactory;
  60. import org.apache.fop.apps.Fop;
  61. import org.apache.fop.apps.MimeConstants;
  62. /*..*/
  63. // Step 1: Construct a FopFactory
  64. // (reuse if you plan to render multiple documents!)
  65. FopFactory fopFactory = FopFactory.newInstance();
  66. // Step 2: Set up output stream.
  67. // Note: Using BufferedOutputStream for performance reasons (helpful with FileOutputStreams).
  68. OutputStream out = new BufferedOutputStream(new FileOutputStream(new File("C:/Temp/myfile.pdf")));
  69. try {
  70. // Step 3: Construct fop with desired output format
  71. Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, out);
  72. // Step 4: Setup JAXP using identity transformer
  73. TransformerFactory factory = TransformerFactory.newInstance();
  74. Transformer transformer = factory.newTransformer(); // identity transformer
  75. // Step 5: Setup input and output for XSLT transformation
  76. // Setup input stream
  77. Source src = new StreamSource(new File("C:/Temp/myfile.fo"));
  78. // Resulting SAX events (the generated FO) must be piped through to FOP
  79. Result res = new SAXResult(fop.getDefaultHandler());
  80. // Step 6: Start XSLT transformation and FOP processing
  81. transformer.transform(src, res);
  82. } finally {
  83. //Clean-up
  84. out.close();
  85. }]]></source>
  86. <p>
  87. Let's discuss these 5 steps in detail:
  88. </p>
  89. <ul>
  90. <li>
  91. <strong>Step 1:</strong> You create a new FopFactory instance. The FopFactory instance holds
  92. references to configuration information and cached data. It's important to reuse this
  93. instance if you plan to render multiple documents during a JVM's lifetime.
  94. </li>
  95. <li>
  96. <strong>Step 2:</strong> You set up an OutputStream that the generated document
  97. will be written to. It's a good idea to buffer the OutputStream as demonstrated
  98. to improve performance.
  99. </li>
  100. <li>
  101. <strong>Step 3:</strong> You create a new Fop instance through one of the factory
  102. methods on the FopFactory. You tell the FopFactory what your desired output format
  103. is. This is done by using the MIME type of the desired output format (ex. "application/pdf").
  104. You can use one of the MimeConstants.* constants. The second parameter is the
  105. OutputStream you've setup up in step 2.
  106. </li>
  107. <li>
  108. <strong>Step 4</strong> We recommend that you use JAXP Transformers even
  109. if you don't do XSLT transformations to generate the XSL-FO file. This way
  110. you can always use the same basic pattern. The example here sets up an
  111. "identity transformer" which just passes the input (Source) unchanged to the
  112. output (Result). You don't have to work with a SAXParser if you don't do any
  113. XSLT transformations.
  114. </li>
  115. <li>
  116. <strong>Step 5:</strong> Here you set up the input and output for the XSLT
  117. transformation. The Source object is set up to load the "myfile.fo" file.
  118. The Result is set up so the output of the XSLT transformation is sent to FOP.
  119. The FO file is sent to FOP in the form of SAX events which is the most efficient
  120. way. Please always avoid saving intermediate results to a file or a memory buffer
  121. because that affects performance negatively.
  122. </li>
  123. <li>
  124. <strong>Step 6:</strong> Finally, we start the XSLT transformation by starting
  125. the JAXP Transformer. As soon as the JAXP Transformer starts to send its output
  126. to FOP, FOP itself starts its processing in the background. When the
  127. <code>transform()</code> method returns FOP will also have finished converting
  128. the FO file to a PDF file and you can close the OutputStream.
  129. <note label="Tip!">
  130. It's a good idea to enclose the whole conversion in a try..finally statement. If
  131. you close the OutputStream in the finally section, this will make sure that the
  132. OutputStream is properly closed even if an exception occurs during the conversion.
  133. </note>
  134. </li>
  135. </ul>
  136. <p>
  137. If you're not totally familiar with JAXP Transformers, please have a look at the
  138. <a href="#examples">Embedding examples</a> below. The section contains examples
  139. for all sorts of use cases. If you look at all of them in turn you should be able
  140. to see the patterns in use and the flexibility this approach offers without adding
  141. too much complexity.
  142. </p>
  143. <p>
  144. This may look complicated at first, but it's really just the combination of an
  145. XSL transformation and a FOP run. It's also easy to comment out the FOP part
  146. for debugging purposes, for example when you're tracking down a bug in your
  147. stylesheet. You can easily write the XSL-FO output from the XSL transformation
  148. to a file to check if that part generates the expected output. An example for that
  149. can be found in the <a href="#examples">Embedding examples</a> (See "ExampleXML2FO").
  150. </p>
  151. <section id="basic-logging">
  152. <title>Logging</title>
  153. <p>
  154. Logging is now a little different than it was in FOP 0.20.5. We've switched from
  155. Avalon Logging to <a href="ext:jakarta/commons/logging">Jakarta Commons Logging</a>.
  156. While with Avalon Logging the loggers were directly given to FOP, FOP now retrieves
  157. its logger(s) through a statically available LogFactory. This is similar to the
  158. general pattern that you use when you work with Apache Log4J directly, for example.
  159. We call this "static logging" (Commons Logging, Log4J) as opposed to "instance logging"
  160. (Avalon Logging). This has a consequence: You can't give FOP a logger for each
  161. processing run anymore. The log output of multiple, simultaneously running FOP instances
  162. is sent to the same logger.
  163. </p>
  164. <note>
  165. We know this may be an issue in multi-threaded server environments if you'd like to
  166. know what's going on in every single FOP processing run. We're planning to add an
  167. additional feedback facility to FOP which can be used to obtain all sorts of specific
  168. feedback (validation messages, layout problems etc.). "Static logging" is mainly
  169. interesting for a developer working on FOP and for advanced users who are debugging
  170. FOP. We don't consider the logging output to be useful to normal FOP users. Please
  171. have some patience until we can add this feature or jump in and help us build it. We've
  172. set up a <a href="http://wiki.apache.org/xmlgraphics-fop/ProcessingFeedback">Wiki page</a>
  173. which documents what we're going to build.
  174. </note>
  175. <p>
  176. By default, <a href="ext:jakarta/commons/logging">Jakarta Commons Logging</a> uses
  177. JDK logging (available in JDKs 1.4 or higher) as its backend. You can configure Commons
  178. Logging to use an alternative backend, for example Log4J. Please consult the
  179. <a href="ext:jakarta/commons/logging">documentation for Jakarta Commons Logging</a> on
  180. how to configure alternative backends.
  181. </p>
  182. </section>
  183. <section id="render">
  184. <title>Processing XSL-FO</title>
  185. <p>
  186. Once the Fop instance is set up, call <code>getDefaultHandler()</code> to obtain a SAX
  187. DefaultHandler instance to which you can send the SAX events making up the XSL-FO
  188. document you'd like to render. FOP processing starts as soon as the DefaultHandler's
  189. <code>startDocument()</code> method is called. Processing stops again when the
  190. DefaultHandler's <code>endDocument()</code> method is called. Please refer to the basic
  191. usage pattern shown above to render a simple XSL-FO document.
  192. </p>
  193. </section>
  194. <section id="render-with-xslt">
  195. <title>Processing XSL-FO generated from XML+XSLT</title>
  196. <p>
  197. If you want to process XSL-FO generated from XML using XSLT we recommend
  198. again using standard JAXP to do the XSLT part and piping the generated SAX
  199. events directly through to FOP. The only thing you'd change to do that
  200. on the basic usage pattern above is to set up the Transformer differently:
  201. </p>
  202. <source><![CDATA[
  203. //without XSLT:
  204. //Transformer transformer = factory.newTransformer(); // identity transformer
  205. //with XSLT:
  206. Source xslt = new StreamSource(new File("mystylesheet.xsl"));
  207. Transformer transformer = factory.newTransformer(xslt);]]></source>
  208. </section>
  209. </section>
  210. <section id="input">
  211. <title>Input Sources</title>
  212. <p>
  213. The input XSL-FO document is always received by FOP as a SAX stream (see the
  214. <a href="../dev/design/parsing.html">Parsing Design Document</a> for the rationale).
  215. </p>
  216. <p>
  217. However, you may not always have your input document available as a SAX stream.
  218. But with JAXP it's easy to convert different input sources to a SAX stream so you
  219. can pipe it into FOP. That sounds more difficult than it is. You simply have
  220. to set up the right Source instance as input for the JAXP transformation.
  221. A few examples:
  222. </p>
  223. <ul>
  224. <li>
  225. <strong>URL:</strong> <code>Source src = new StreamSource("http://localhost:8080/testfile.xml");</code>
  226. </li>
  227. <li>
  228. <strong>File:</strong> <code>Source src = new StreamSource(new File("C:/Temp/myinputfile.xml"));</code>
  229. </li>
  230. <li>
  231. <strong>String:</strong> <code>Source src = new StreamSource(new StringReader(myString)); // myString is a String</code>
  232. </li>
  233. <li>
  234. <strong>InputStream:</strong> <code>Source src = new StreamSource(new MyInputStream(something));</code>
  235. </li>
  236. <li>
  237. <strong>Byte Array:</strong> <code>Source src = new StreamSource(new ByteArrayInputStream(myBuffer)); // myBuffer is a byte[] here</code>
  238. </li>
  239. <li>
  240. <strong>DOM:</strong> <code>Source src = new DOMSource(myDocument); // myDocument is a Document or a Node</code>
  241. </li>
  242. <li>
  243. <strong>Java Objects:</strong> Please have a look at the <a href="#examples">Embedding examples</a> which contain an example for this.
  244. </li>
  245. </ul>
  246. <p>
  247. There are a variety of upstream data manipulations possible.
  248. For example, you may have a DOM and an XSL stylesheet; or you may want to
  249. set variables in the stylesheet. Interface documentation and some cookbook
  250. solutions to these situations are provided in
  251. <a href="http://xml.apache.org/xalan-j/usagepatterns.html">Xalan Basic Usage Patterns</a>.
  252. </p>
  253. </section>
  254. <section id="config-internal">
  255. <title>Configuring Apache FOP Programmatically</title>
  256. <p>
  257. Apache FOP provides two levels on which you can customize FOP's
  258. behaviour: the FopFactory and the user agent.
  259. </p>
  260. <section id="fop-factory">
  261. <title>Customizing the FopFactory</title>
  262. <p>
  263. The FopFactory holds configuration data and references to objects which are reusable over
  264. multiple rendering runs. It's important to instantiate it only once (except in special
  265. environments) and reuse it every time to create new FOUserAgent and Fop instances.
  266. </p>
  267. <p>
  268. You can set all sorts of things on the FopFactory:
  269. </p>
  270. <ul>
  271. <li>
  272. <p>
  273. The <strong>font base URL</strong> to use when resolving relative URLs for fonts. Example:
  274. </p>
  275. <source>fopFactory.setFontBaseURL("file:///C:/Temp/fonts");</source>
  276. </li>
  277. <li>
  278. <p>
  279. Disable <strong>strict validation</strong>. When disabled FOP is less strict about the rules
  280. established by the XSL-FO specification. Example:
  281. </p>
  282. <source>fopFactory.setStrictValidation(false);</source>
  283. </li>
  284. <li>
  285. <p>
  286. Enable an <strong>alternative set of rules for text indents</strong> that tries to mimic the behaviour of many commercial
  287. FO implementations, that chose to break the specification in this respect. The default of this option is
  288. 'false', which causes Apache FOP to behave exactly as described in the specification. To enable the
  289. alternative behaviour, call:
  290. </p>
  291. <source>fopFactory.setBreakIndentInheritanceOnReferenceAreaBoundary(true);</source>
  292. </li>
  293. <li>
  294. <p>
  295. Set the <strong>source resolution</strong> for the document. This is used internally to determine the pixel
  296. size for SVG images and bitmap images without resolution information. Default: 72 dpi. Example:
  297. </p>
  298. <source>fopFactory.setSourceResolution(96); // =96dpi (dots/pixels per Inch)</source>
  299. </li>
  300. <li>
  301. <p>
  302. Manually add an <strong>ElementMapping instance</strong>. If you want to supply a special FOP extension
  303. you can give the instance to the FOUserAgent. Normally, the FOP extensions can be automatically detected
  304. (see the documentation on extension for more info). Example:
  305. </p>
  306. <source>fopFactory.addElementMapping(myElementMapping); // myElementMapping is a org.apache.fop.fo.ElementMapping</source>
  307. </li>
  308. <li>
  309. <p>
  310. Set a <strong>URIResolver</strong> for custom URI resolution. By supplying a JAXP URIResolver you can add
  311. custom URI resolution functionality to FOP. For example, you can use
  312. <a href="ext:xml.apache.org/commons/resolver">Apache XML Commons Resolver</a> to make use of XCatalogs. Example:
  313. </p>
  314. <source>fopFactory.setURIResolver(myResolver); // myResolver is a javax.xml.transform.URIResolver</source>
  315. <note>
  316. Both the FopFactory and the FOUserAgent have a method to set a URIResolver. The URIResolver on the FopFactory
  317. is primarily used to resolve URIs on factory-level (hyphenation patterns, for example) and it is always used
  318. if no other URIResolver (for example on the FOUserAgent) resolved the URI first.
  319. </note>
  320. </li>
  321. </ul>
  322. </section>
  323. <section id="user-agent">
  324. <title>Customizing the User Agent</title>
  325. <p>
  326. The user agent is the entity that allows you to interact with a single rendering run, i.e. the processing of a single
  327. document. If you wish to customize the user agent's behaviour, the first step is to create your own instance
  328. of FOUserAgent using the appropriate factory method on FopFactory and pass that
  329. to the factory method that will create a new Fop instance:
  330. </p>
  331. <source><![CDATA[
  332. FopFactory fopFactory = FopFactory.newInstance(); // Reuse the FopFactory if possible!
  333. // do the following for each new rendering run
  334. FOUserAgent userAgent = fopFactory.newFOUserAgent();
  335. // customize userAgent
  336. Fop fop = fopFactory.newFop(MimeConstants.MIME_POSTSCRIPT, userAgent, out);]]></source>
  337. <p>
  338. You can do all sorts of things on the user agent:
  339. </p>
  340. <ul>
  341. <li>
  342. <p>
  343. The <strong>base URL</strong> to use when resolving relative URLs. Example:
  344. </p>
  345. <source>userAgent.setBaseURL("file:///C:/Temp/");</source>
  346. </li>
  347. <li>
  348. <p>
  349. Set the <strong>producer</strong> of the document. This is metadata information that can be used for certain output formats such as PDF. The default producer is "Apache FOP". Example:
  350. </p>
  351. <source>userAgent.setProducer("MyKillerApplication");</source>
  352. </li>
  353. <li>
  354. <p>
  355. Set the <strong>creating user</strong> of the document. This is metadata information that can be used for certain output formats such as PDF. Example:
  356. </p>
  357. <source>userAgent.setCreator("John Doe");</source>
  358. </li>
  359. <li>
  360. <p>
  361. Set the <strong>author</strong> of the document. This is metadata information that can be used for certain output formats such as PDF. Example:
  362. </p>
  363. <source>userAgent.setAuthor("John Doe");</source>
  364. </li>
  365. <li>
  366. <p>
  367. Override the <strong>creation date and time</strong> of the document. This is metadata information that can be used for certain output formats such as PDF. Example:
  368. </p>
  369. <source>userAgent.setCreationDate(new Date());</source>
  370. </li>
  371. <li>
  372. <p>
  373. Set the <strong>title</strong> of the document. This is metadata information that can be used for certain output formats such as PDF. Example:
  374. </p>
  375. <source>userAgent.setTitle("Invoice No 138716847");</source>
  376. </li>
  377. <li>
  378. <p>
  379. Set the <strong>keywords</strong> of the document. This is metadata information that can be used for certain output formats such as PDF. Example:
  380. </p>
  381. <source>userAgent.setKeywords("XML XSL-FO");</source>
  382. </li>
  383. <li>
  384. <p>
  385. Set the <strong>target resolution</strong> for the document. This is used to
  386. specify the output resolution for bitmap images generated by bitmap renderers
  387. (such as the TIFF renderer) and by bitmaps generated by Apache Batik for filter
  388. effects and such. Default: 72 dpi. Example:
  389. </p>
  390. <source>userAgent.setTargetResolution(300); // =300dpi (dots/pixels per Inch)</source>
  391. </li>
  392. <li>
  393. <p>
  394. Set <strong>your own Renderer instance</strong>. If you want to supply your own renderer or
  395. configure a Renderer in a special way you can give the instance to the FOUserAgent. Normally,
  396. the Renderer instance is created by FOP. Example:
  397. </p>
  398. <source>userAgent.setRendererOverride(myRenderer); // myRenderer is an org.apache.fop.render.Renderer</source>
  399. </li>
  400. <li>
  401. <p>
  402. Set <strong>your own FOEventHandler instance</strong>. If you want to supply your own FOEventHandler or
  403. configure an FOEventHandler subclass in a special way you can give the instance to the FOUserAgent. Normally,
  404. the FOEventHandler instance is created by FOP. Example:
  405. </p>
  406. <source>userAgent.setFOEventHandlerOverride(myFOEventHandler); // myFOEventHandler is an org.apache.fop.fo.FOEventHandler</source>
  407. </li>
  408. <li>
  409. <p>
  410. Set a <strong>URIResolver</strong> for custom URI resolution. By supplying a JAXP URIResolver you can add
  411. custom URI resolution functionality to FOP. For example, you can use
  412. <a href="ext:xml.apache.org/commons/resolver">Apache XML Commons Resolver</a> to make use of XCatalogs. Example:
  413. </p>
  414. <source>userAgent.setURIResolver(myResolver); // myResolver is a javax.xml.transform.URIResolver</source>
  415. <note>
  416. Both the FopFactory and the FOUserAgent have a method to set a URIResolver. The URIResolver on the FOUserAgent is
  417. used for resolving URIs which are document-related. If it's not set or cannot resolve a URI, the URIResolver
  418. from the FopFactory is used.
  419. </note>
  420. </li>
  421. </ul>
  422. <note>
  423. You should not reuse an FOUserAgent instance between FOP rendering runs although you can. Especially
  424. in multi-threaded environment, this is a bad idea.
  425. </note>
  426. </section>
  427. </section>
  428. <section id="config-external">
  429. <title>Using a Configuration File</title>
  430. <p>
  431. Instead of setting the parameters manually in code as shown above you can also set
  432. many values from an XML configuration file:
  433. </p>
  434. <source><![CDATA[
  435. import org.apache.avalon.framework.configuration.Configuration;
  436. import org.apache.avalon.framework.configuration.DefaultConfigurationBuilder;
  437. /*..*/
  438. DefaultConfigurationBuilder cfgBuilder = new DefaultConfigurationBuilder();
  439. Configuration cfg = cfgBuilder.buildFromFile(new File("C:/Temp/mycfg.xml"));
  440. fopFactory.setUserConfig(cfg);
  441. /* ..or.. */
  442. fopFactory.setUserConfig(new File("C:/Temp/mycfg.xml"));]]></source>
  443. <p>
  444. The layout of the configuration file is described on the <a href="configuration.html">Configuration page</a>.
  445. </p>
  446. </section>
  447. <section id="hints">
  448. <title>Hints</title>
  449. <section id="object-reuse">
  450. <title>Object reuse</title>
  451. <p>
  452. Fop instances shouldn't (and can't) be reused. Please recreate
  453. Fop and FOUserAgent instances for each rendering run using the FopFactory.
  454. This is a cheap operation as all reusable information is held in the
  455. FopFactory. That's why it's so important to reuse the FopFactory instance.
  456. </p>
  457. </section>
  458. <section id="awt">
  459. <title>AWT issues</title>
  460. <p>
  461. If your XSL-FO files contain SVG then Apache Batik will be used. When Batik is
  462. initialised it uses certain classes in <code>java.awt</code> that
  463. intialise the Java AWT classes. This means that a daemon thread
  464. is created by the JVM and on Unix it will need to connect to a
  465. DISPLAY.
  466. </p>
  467. <p>
  468. The thread means that the Java application may not automatically quit
  469. when finished, you will need to call <code>System.exit()</code>. These
  470. issues should be fixed in the JDK 1.4.
  471. </p>
  472. <p>
  473. If you run into trouble running FOP on a head-less server, please see the
  474. <a href="graphics.html#batik">notes on Batik</a>.
  475. </p>
  476. </section>
  477. <section id="render-info">
  478. <title>Getting information on the rendering process</title>
  479. <p>
  480. To get the number of pages that were rendered by FOP you can call
  481. <code>Fop.getResults()</code>. This returns a <code>FormattingResults</code> object
  482. where you can look up the number of pages produced. It also gives you the
  483. page-sequences that were produced along with their id attribute and their
  484. numbers of pages. This is particularly useful if you render multiple
  485. documents (each enclosed by a page-sequence) and have to know the number of
  486. pages of each document.
  487. </p>
  488. </section>
  489. </section>
  490. <section id="performance">
  491. <title>Improving performance</title>
  492. <p>
  493. There are several options to consider:
  494. </p>
  495. <ul>
  496. <li>
  497. Whenever possible, try to use SAX to couple the individual components involved
  498. (parser, XSL transformer, SQL datasource etc.).
  499. </li>
  500. <li>
  501. Depending on the target OutputStream (in case of a FileOutputStream, but not
  502. for a ByteArrayOutputStream, for example) it may improve performance considerably
  503. if you buffer the OutputStream using a BufferedOutputStream:
  504. <code>out = new java.io.BufferedOutputStream(out);</code>
  505. <br/>
  506. Make sure you properly close the OutputStream when FOP is finished.
  507. </li>
  508. <li>
  509. Cache the stylesheet. If you use the same stylesheet multiple times
  510. you can set up a JAXP <code>Templates</code> object and reuse it each time you do
  511. the XSL transformation. (More information can be found
  512. <a class="fork" href="http://www.javaworld.com/javaworld/jw-05-2003/jw-0502-xsl.html">here</a>.)
  513. </li>
  514. <li>
  515. Use an XSLT compiler like <a class="fork" href="http://xml.apache.org/xalan-j/xsltc_usage.html">XSLTC</a>
  516. that comes with Xalan-J.
  517. </li>
  518. <li>
  519. Fine-tune your stylesheet to make the XSLT process more efficient and to create XSL-FO that can
  520. be processed by FOP more efficiently. Less is more: Try to make use of property inheritance where possible.
  521. </li>
  522. </ul>
  523. </section>
  524. <section id="multithreading">
  525. <title>Multithreading FOP</title>
  526. <p>
  527. Apache FOP may currently not be completely thread safe.
  528. The code has not been fully tested for multi-threading issues, yet.
  529. If you encounter any suspicious behaviour, please notify us.
  530. </p>
  531. <p>
  532. There is also a known issue with fonts being jumbled between threads when using
  533. the Java2D/AWT renderer (which is used by the -awt and -print output options).
  534. In general, you cannot safely run multiple threads through the AWT renderer.
  535. </p>
  536. </section>
  537. <section id="examples">
  538. <title>Examples</title>
  539. <p>
  540. The directory "{fop-dir}/examples/embedding" contains several working examples.
  541. </p>
  542. <section id="ExampleFO2PDF">
  543. <title>ExampleFO2PDF.java</title>
  544. <p>This
  545. <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleFO2PDF.java?view=markup">
  546. example</a>
  547. demonstrates the basic usage pattern to transform an XSL-FO
  548. file to PDF using FOP.
  549. </p>
  550. <figure src="images/EmbeddingExampleFO2PDF.png" alt="Example XSL-FO to PDF"/>
  551. </section>
  552. <section id="ExampleXML2FO">
  553. <title>ExampleXML2FO.java</title>
  554. <p>This
  555. <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleXML2FO.java?view=markup">
  556. example</a>
  557. has nothing to do with FOP. It is there to show you how an XML
  558. file can be converted to XSL-FO using XSLT. The JAXP API is used to do the
  559. transformation. Make sure you've got a JAXP-compliant XSLT processor in your
  560. classpath (ex. <a href="http://xml.apache.org/xalan-j">Xalan</a>).
  561. </p>
  562. <figure src="images/EmbeddingExampleXML2FO.png" alt="Example XML to XSL-FO"/>
  563. </section>
  564. <section id="ExampleXML2PDF">
  565. <title>ExampleXML2PDF.java</title>
  566. <p>This
  567. <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleXML2PDF.java?view=markup">
  568. example</a>
  569. demonstrates how you can convert an arbitrary XML file to PDF
  570. using XSLT and XSL-FO/FOP. It is a combination of the first two examples
  571. above. The example uses JAXP to transform the XML file to XSL-FO and FOP to
  572. transform the XSL-FO to PDF.
  573. </p>
  574. <figure src="images/EmbeddingExampleXML2PDF.png" alt="Example XML to PDF (via XSL-FO)"/>
  575. <p>
  576. The output (XSL-FO) from the XSL transformation is piped through to FOP using
  577. SAX events. This is the most efficient way to do this because the
  578. intermediate result doesn't have to be saved somewhere. Often, novice users
  579. save the intermediate result in a file, a byte array or a DOM tree. We
  580. strongly discourage you to do this if it isn't absolutely necessary. The
  581. performance is significantly higher with SAX.
  582. </p>
  583. </section>
  584. <section id="ExampleObj2XML">
  585. <title>ExampleObj2XML.java</title>
  586. <p>This
  587. <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleObj2XML.java?view=markup">
  588. example</a>
  589. is a preparatory example for the next one. It's an example that
  590. shows how an arbitrary Java object can be converted to XML. It's an often
  591. needed task to do this. Often people create a DOM tree from a Java object and
  592. use that. This is pretty straightforward. The example here, however, shows how
  593. to do this using SAX, which will probably be faster and not even more
  594. complicated once you know how this works.
  595. </p>
  596. <figure src="images/EmbeddingExampleObj2XML.png" alt="Example Java object to XML"/>
  597. <p>
  598. For this example we've created two classes: ProjectTeam and ProjectMember
  599. (found in xml-fop/examples/embedding/java/embedding/model). They represent
  600. the same data structure found in
  601. xml-fop/examples/embedding/xml/xml/projectteam.xml. We want to serialize to XML a
  602. project team with several members which exist as Java objects.
  603. Therefore we created the two classes: ProjectTeamInputSource and
  604. ProjectTeamXMLReader (in the same place as ProjectTeam above).
  605. </p>
  606. <p>
  607. The XMLReader implementation (regard it as a special kind of XML parser) is
  608. responsible for creating SAX events from the Java object. The InputSource
  609. class is only used to hold the ProjectTeam object to be used.
  610. </p>
  611. <p>
  612. Have a look at the source of ExampleObj2XML.java to find out how this is
  613. used. For more detailed information see other resources on JAXP (ex.
  614. <a class="fork" href="http://java.sun.com/xml/jaxp/dist/1.1/docs/tutorial/xslt/3_generate.html">An older JAXP tutorial</a>).
  615. </p>
  616. </section>
  617. <section id="ExampleObj2PDF">
  618. <title>ExampleObj2PDF.java</title>
  619. <p>This
  620. <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleObj2PDF.java?view=markup">
  621. example</a>
  622. combines the previous and the third to demonstrate
  623. how you can transform a Java object to a PDF directly in one smooth run
  624. by generating SAX events from the Java object that get fed to an XSL
  625. transformation. The result of the transformation is then converted to PDF
  626. using FOP as before.
  627. </p>
  628. <figure src="images/EmbeddingExampleObj2PDF.png" alt="Example Java object to PDF (via XML and XSL-FO)"/>
  629. </section>
  630. <section id="ExampleDOM2PDF">
  631. <title>ExampleDOM2PDF.java</title>
  632. <p>This
  633. <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleDOM2PDF.java?view=markup">
  634. example</a>
  635. has FOP use a DOMSource instead of a StreamSource in order to
  636. use a DOM tree as input for an XSL transformation.
  637. </p>
  638. </section>
  639. <section id="ExampleSVG2PDF">
  640. <title>ExampleSVG2PDF.java (PDF Transcoder example)</title>
  641. <p>This
  642. <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleSVG2PDF.java?view=markup">
  643. example</a>
  644. shows the usage of the PDF Transcoder, a sub-application within FOP.
  645. It is used to generate a PDF document from an SVG file.
  646. </p>
  647. </section>
  648. <section id="example-notes">
  649. <title>Final notes</title>
  650. <p>
  651. These examples should give you an idea of what's possible. It should be easy
  652. to adjust these examples to your needs. Also, if you have other examples that you
  653. think should be added here, please let us know via either the fop-users or fop-dev
  654. mailing lists. Finally, for more help please send your questions to the fop-users
  655. mailing list.
  656. </p>
  657. </section>
  658. </section>
  659. </body>
  660. </document>