Bernd Brandstetter wrote:
I had a similar problem some time ago when I tried to create a PDF
containing hundreds of SVG images. I finally got it to work by disabling
image caching completely by commenting out the line 267
"m_urlMap.put(href, imageInstance);" in FopImageFactory.java (fop-0.20.5)
This wont help much (and probably even hurt) for most bitmap image
formats, because the associated PDF XObject which also refers to the
pixel array hangs around until the PDF object dictionary is written,
which is just before the result stream is finished. Unfortunately
this can't be changed easily in the 0.20.x branch.
It would be nice if the next version of fop could provide a means to either
turn off image caching (as a configuration option) or to limit the cache
size.
The redesigned code apparently discards pixel information after it
is written to the result stream, and it also supports reuse of
PDF objects better, so this may be actually implemented. Note that
limiting the cache size can lead to unexpected behaviour for
dynamically generated images.
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
