On 24 Jun 2009, at 15:34, Georg Datterl wrote:
Hi Georg
> <snip />
> Maybe that's helpfull.
Definitely! I just looked at the code for
org.apache.fop.area.inline.UnresolvedPageNumber, and the issue is that
those areas are serializable, but the Font instance member is
explicitly declared as 'transient', which means it will never be
serialized/deserialized.
> What I find interesting is, the error appears somewhere after
> generating all the pages, since the table of contents is far earlier
> than Position 25986. I guess, it appears when the page-number-
> citation is revisited with the actual page numbers.
Indeed.
> Are there any requirements for using setConserveMemoryPolicy? I only
> added the above line, because I have long page sequences I can not
> shorten.
>
The setConserveMemoryPolicy() option was introduced into Trunk fairly
recently.
Currently, its only effect is precisely to serialize pages containing
unresolved forward references to disk, to avoid having to keep them in
memory until they can be resolved.
If the document runs without enabling that option, then there's your
workaround for the moment.
If your TOC is in a separate page-sequence (with its own numbering),
you could also consider moving it to the end of the FO file. Using the
new IF or area tree XML, it should prove rather easy to relocate the
corresponding pages to the beginning of the document. Such a strategy
would at least avoid forward references (may also lead to a much
better-looking layout, since all the page-numbers would be known)
Thanks for the extra info. I'll look deeper into it as soon as I see
the opportunity.
Regards
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail:
fop-users-unsubscribe@...
For additional commands, e-mail:
fop-users-help@...
