Fop crashes at table-omit-header-at-break="true" on line 744. If I change to "false" runs OK. See attached file. Using java version "1.6.0_11" Java(TM) SE Runtime Environment (build 1.6.0_11-b03) Java HotSpot(TM) Client VM (build 11.0-b16, mixed mode, sharing) Here are the generated errors: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\WINDOWS\system32>r: R:\>cd xml\fop R:\xml\fop>fop -fo fop_error.fo -pdf fop_error.pdf Dec 15, 2008 3:26:56 PM org.apache.fop.cli.Main startFOP SEVERE: Exception java.lang.NullPointerException at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:168) at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115) at org.apache.fop.cli.Main.startFOP(Main.java:166) at org.apache.fop.cli.Main.main(Main.java:197) --------- java.lang.NullPointerException at org.apache.fop.layoutmgr.table.RowPainter.addAreasAndFlushRow(RowPain ter.java:149) at org.apache.fop.layoutmgr.table.TableContentLayoutManager.iterateAndPa intPositions(TableContentLayoutManager.java:757) at org.apache.fop.layoutmgr.table.TableContentLayoutManager.addAreas(Tab leContentLayoutManager.java:694) at org.apache.fop.layoutmgr.table.TableLayoutManager.addAreas(TableLayou tManager.java:334) at org.apache.fop.layoutmgr.BlockLayoutManager.addAreas(BlockLayoutManag er.java:393) at org.apache.fop.layoutmgr.AreaAdditionUtil.addAreas(AreaAdditionUtil.j ava:118) at org.apache.fop.layoutmgr.FlowLayoutManager.addAreas(FlowLayoutManager .java:297) at org.apache.fop.layoutmgr.PageBreaker.addAreas(PageBreaker.java:241) at org.apache.fop.layoutmgr.AbstractBreaker.addAreas(AbstractBreaker.jav a:507) at org.apache.fop.layoutmgr.AbstractBreaker.addAreas(AbstractBreaker.jav a:370) at org.apache.fop.layoutmgr.PageBreaker.doPhase3(PageBreaker.java:262) at org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.jav a:345) at org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.jav a:263) at org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(Pag eSequenceLayoutManager.java:144) at org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.j ava:233) at org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java :145) at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilde r.java:378) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:194) at org.apache.xalan.transformer.TransformerIdentityImpl.endElement(Trans formerIdentityImpl.java:1101) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source ) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknow n Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContent Dispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Un known Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xalan.transformer.TransformerIdentityImpl.transform(Transf ormerIdentityImpl.java:484) at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:165) at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115) at org.apache.fop.cli.Main.startFOP(Main.java:166) at org.apache.fop.cli.Main.main(Main.java:197) R:\xml\fop>
Created attachment 23026 [details] fo file generated from saxon v. 6.5.2
Comment on attachment 23026 [details] fo file generated from saxon v. 6.5.2 sorry...to be more specific, problem is with the last table-omit-header-at-break="true" in the file
Hi, Thanks for your bug report. Please upgrade to FOP version 0.95 that doesn't crash on your file. Unfortunately, due to our limited resources we can't afford to provide bug-fix releases for versions other than the latest one (0.95 at the moment). However, when processing your file FOP Trunk issues a 'severe' warning about a situation that isn't supposed to happen. I'll leave this bug open for the moment as I'd like to investigate the case. Thanks, Vincent
This looks fixed in 0.95.
resetting severity from major to normal pending further review
resetting P2 open bugs to P3 pending further review