xmlgraphics-fop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthias Schwarz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FOP-2684) NoSuchElementException in LMiter.next() with page breaks and different page masters
Date Fri, 14 Jun 2019 11:11:00 GMT

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

Matthias Schwarz commented on FOP-2684:

I might be running into the same, or a very similar issue. At least the stack trace and the
description look very related. The only difference is that it doesn't include a list, but
a block which spans between two pages having different margins set.

I'm able to reproduce this in FOP 2.3 and FOP 2.1. I didn't try with 2.2. In 2.1 I'm running
into a NullpointerException though.

Here is the simpliefied FO I am able to reproduce it with: [^fop-2684.fo]

Also here is my log output for 2.3: [^fop-2684.log]

^In my case the workaround is to put a keep-together-within-page on the block would span over
to the 2nd page otherwise.^

In case you think I should create a different issue for it, please notify me.

> NoSuchElementException in LMiter.next() with page breaks and different page masters
> -----------------------------------------------------------------------------------
>                 Key: FOP-2684
>                 URL: https://issues.apache.org/jira/browse/FOP-2684
>             Project: FOP
>          Issue Type: Bug
>    Affects Versions: 2.1
>         Environment: Windows 10, jdk1.8.0_112 (64bit)
>            Reporter: Michael Klein
>            Priority: Major
>         Attachments: Exception.fo, Stacktrace.txt, fop-2684.fo, fop-2684.log
> I have a big FO instance which results in a NoSuchElementException.
> To reproduce this issue, I was able to created a simple FO with different page masters
for left and right pages and a list at the end of the first page which first item is too long
for be rendered on the first page.
> When using a simple page master for all pages or a block instead of a list item, everything
works as expected.

This message was sent by Atlassian JIRA

View raw message