It may contain the necessary information to understand and resolve the problem. The following list will hopefully help you to identify and correct those problems.Ĭheck the Compliance page for the feature causing trouble. When you use your existing FO files or XML/XSL files which work fine with FOP version 0.20.5 against this FOP version some things may not work as expected. The SVG Renderer and the MIF Handler have not been resurrected, yet! They are currently non-functional and hope for someone to step up and reimplement them. While FOP 0.20.5 allowed you to have empty fo:table-cell elements, the new code will complain about that (unless relaxed validation is enabled) because the specification demands at least one block-level element ( (%block )+, see XSL-FO 1.1, 6.7.10) inside an fo:table-cell element.Įxtensions and Renderers written for version 0.20.5 will not work with the new code! The new FOP extension for Barcode4J is available since January 2007. FOP 0.20.5 contains many bugs which have been corrected in the new code. Things that worked fine in version 0.20.5 might start to produce warnings or even errors now. The new code is much more strict about the interpretation of the XSL-FO 1.1 specification. In the unlikely case that due to a bug you still need to use font metrics files you will need to regenerate the font metrics file if yours are from a FOP version before 0.93. A XML Schema file can be found under src/foschema/fop-configuration.xsd.īeginning with version 0.94 you can skip the generation of font metric files and remove the 'font-metrics' attribute in the font configuration. See conf/fop.xconf for an example configuration file. The format of the configuration files has changed since version 0.20.5. If you are using a configuration file for version 0.20.5, you have to rebuild it in the new format. Similarly if you upgrade from 0.92 and use deprecated methods. If you upgrade from 0.91 beta, you will need to adjust your Java code. Since version 0.92 some deprecated methods which were part of the old API have been removed.

Version 0.92 introduced the new stable API. The API of FOP has changed considerably and is not backwards-compatible with versions 0.20.5 and 0.91beta. With version 0.93 the code has reached production level, and continues to improve with version 0.94. More than half of the codebase has been rewritten over the last three years. If you're planning to upgrade to the latest Apache™ FOP version there are a few very important things to consider: Upgrading from an Earlier Version of Apache™ FOP Important!

Hope to see you there! ApacheCon Europe ¶ Search Apache XML Graphics ¶ ApacheCon N.

Apache ant versions years