[ 
https://issues.apache.org/jira/browse/FOP-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081125#comment-15081125
 ] 

Radu Coravu commented on FOP-2533:
----------------------------------

Thanks for the update Simon. 
Do you have a clue about when the next Apache FOP (2.1?) will be released?
I'm interested in having some NPEs which were introduced in 2.0 fixed:

https://issues.apache.org/jira/browse/FOP-2461

> PDF generation never stops when you have a missing defined region name
> ----------------------------------------------------------------------
>
>                 Key: FOP-2533
>                 URL: https://issues.apache.org/jira/browse/FOP-2533
>             Project: FOP
>          Issue Type: Bug
>          Components: fo/page
>    Affects Versions: 1.1, 2.0
>            Reporter: Radu Coravu
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> If you try to publish to PDF this XSL-FO file:
> {code}<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format";>
>    <fo:layout-master-set>
>       <fo:simple-page-master master-name="page-initiale" page-width="21cm" 
> page-height="29.7cm">
>          <fo:region-body margin="3cm" region-name="body"/>
>          <fo:region-after extent="2cm" region-name="first-page-footer"/>
>       </fo:simple-page-master>
>       <fo:simple-page-master master-name="pages-standard">
>          <fo:region-body margin-top="3cm"/>
>       </fo:simple-page-master>
>    </fo:layout-master-set>
>    <fo:page-sequence master-reference="page-initiale">
>       <fo:flow flow-name="xsl-region-body">
>          <fo:block></fo:block>
>       </fo:flow>
>    </fo:page-sequence>
>    <fo:page-sequence master-reference="pages-standard">
>       
>       <fo:flow flow-name="xsl-region-body">
>          <fo:block page-break-after="always"/>
>       </fo:flow>
>    </fo:page-sequence>
> </fo:root>{code}
> the generation keeps creating a very large PDF and eventually throws an out 
> of memory.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to