[
https://issues.apache.org/jira/browse/FOP-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim updated FOP-2567:
---------------------
Attachment: NoSuchElementExpTest.zip
Zip containing Data (Studiengangsplan.xml) "broken" template
(HISinOne-freePosition.xsl) and expected outcome (expectedOutput.pdf) for
testing purposes.
> NoSuchElementException in LMiter.next() with absolute positioned
> block-container
> --------------------------------------------------------------------------------
>
> Key: FOP-2567
> URL: https://issues.apache.org/jira/browse/FOP-2567
> Project: FOP
> Issue Type: Bug
> Components: layout/block
> Affects Versions: 2.0
> Environment: reproduceable on Linux and Windows
> Reporter: Tim
> Attachments: NoSuchElementExpTest.zip
>
>
> We recently updated from FOP 1.0 to FOP 2.0.
> Upon Tests, some old templates run into an java.util.NoSuchElementException
> at org.apache.fop.layoutmgr.LMiter.next(LMiter.java:69)
> We found out that an absolute positioned block-container, like this, was the
> problem:
> <fo:block-container position="absolute"
> left="0cm"
> top="0cm"
> right="0cm"
> bottom="0cm">
> When removing the positioning, the template continues to perform as expected.
> Since this problem was not occuring in FOP 1.0 and it seems a bit odd to run
> into a "NoSuchElementException" on an iterator that is checked for length
> before the next Element is fetched, I filled this Bug report.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
