FOP Design

| Introduction |
This is the design for the external interface when FOP is to be embedded inside another java application. Common places where FOP is embedded is in a report production application of a server side application such as Cocoon.
| Settings |
| User Agent |
The user agent is responsible for supplying user or context specific information. The list of user agent values can be found on the User Agent page.
| Logging |
logging level logging messages of various levels error handling Logging setup (LogKit, Log4J, JDK14Logging)
| XML input |
various ways to supply FOP with the xsl:fo file, fo, xml+xsl sax handler
| general options |
base directory uri resolvers which implementation of a particular LayoutManager to use
| Rendering Options |
embedding fonts compression in pdf image embedding for the PS renderer (eventually): PostScript Level PPD to use binary/ascii switch
| User Agent |
Output from FOP: - Generation statistics: Number of pages total, Number of pages of each page-sequence, page-master used for each page (could be used to control the paper bin to get paper from, important for me in conjunction with PS Renderer).
| Setting Up |
The Driver handles the XML input. The user agent information is through the FOUserAgent. We could handle logging through the user agent. Options could also be handled through the user agent, using mime type selection for renderer options.
| Others |
render to more than one renderer at once (maybe not from the command line). For example you could generate a PDF for the archive and the PS for the printer in one run. It would probably be faster than converting the PDF to PostScript afterwards. Several code pieces for resolving URLs and/or file locations are scattered all over FOP and Batik. These should be replaced with an URIResolver invocation to unify behaviour and remove redundancies.

Copyright © 1999-2002 The Apache Software Foundation. All Rights Reserved.