Am 26.03.2012 16:50, schrieb Pravin Chaudhari: > I am receiving below warnings and error while transforming to PDF using > XSL-FO. I m currently using old version of fop.jar. Did we address this issue > in fop1.0? > > [3/23/12 14:41:09:614 CDT] 0000003d PageBreakingA W > org.apache.fop.layoutmgr.PageBreakingAlgorithm updateData2 Part/page 0 > overflows the available area in block-progression dimension. > (fo:static-content, location: 231/50) > [3/23/12 14:41:09:729 CDT] 0000003d PageBreakingA W > org.apache.fop.layoutmgr.PageBreakingAlgorithm updateData2 Part/page 0 > overflows the available area in block-progression dimension. > (fo:static-content, location: 231/50) > [3/23/12 14:41:09:742 CDT] 0000003d PageBreakingA W > org.apache.fop.layoutmgr.PageBreakingAlgorithm updateData2 Part/page 0 > overflows the available area in block-progression dimension. > (fo:static-content, location: 231/50) > [3/23/12 14:41:09:755 CDT] 0000003d PageBreakingA W > org.apache.fop.layoutmgr.PageBreakingAlgorithm updateData2 Part/page 0 > overflows the available area in block-progression dimension. > (fo:static-content, location: 231/50) > [3/23/12 14:41:09:764 CDT] 0000003d PageBreakingA W > org.apache.fop.layoutmgr.PageBreakingAlgorithm updateData2 Part/page 0 > overflows the available area in block-progression dimension. > (fo:static-content, location: 231/50) > [3/23/12 14:41:13:566 CDT] 0000003d FONode W > org.apache.fop.fo.pagination.PageSequenceMaster getNextSimplePageMaster > subsequences exhausted in page-sequence-master 'simpleDocBenefits', using > previous subsequence > [3/23/12 14:41:13:594 CDT] 0000003d FatalErrorExc E > us.mn.state.deed.uitip.framework.log.CommonsLogImpl em Exception occured > while an Action was processing: subsequences exhausted in > page-sequence-master 'simpleDocBenefits', cannot recover > java.lang.IllegalStateException: > subsequences exhausted in page-sequence-master 'simpleDocBenefits', cannot > recover > at > org.apache.fop.layoutmgr.PageProvider.cacheNextPage(PageProvider.java:275)
These are mos likely problems in your XSLFO: > page 0 overflows the available area in block-progression. > (fo:static-content, location: 231/50) This means you've put too much content in a static-content area. If you think your content hight is the same as the available extent of the static content area, it is possible that the overflow is due to round off errors. Unless your output clearly shows an overflow, these warnings are harmless (but check the output anyway) > subsequences exhausted in page-sequence-master This is more serious, it means your body flow generates more pages than there are pages generated by the page master. An example: you can have a page master defining exactly two pages <fo:page-sequence-master master-name="foo"> <fo:single-page-master-reference master-reference="first-page"/> <fo:single-page-master-reference master-reference="next-page"/> </fo:page-sequence-master> If your page sequence generates more than two pages, you'll get the error mentioned above. Check you page master definition accordingly. J.Pietschmann --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
