[FOP-2567] NoSuchElementException in LMiter.next() with absolute positioned block-container

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.0
• Component/s: layout/block
• Environment: reproduceable on Linux and Windows
• Assignee: Unassigned
• Reporter: Tim
• Created: 25/Jan/16 13:11
• Updated: 31/Jan/17 15:15

Description

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.

Issue Links

• is related to: FOP-2684 NoSuchElementException in LMiter.next() with page breaks and different page masters