[daisy] image update is not reflected in the pdf

[Jorg Heymans]

On Wed, Mar 12, 2008 at 12:12 PM, Bruno Dumon <bruno at outerthought.org>
wrote:

> It's FOP who caches the images. When we used the FOP 0.20 series, we had
> a component which cleared FOP's cache from time to time (since otherwise
> it never got evicted and hence could cause memory leaks). I don't know
> how the caching in FOP 0.9 works, and if it's possible to invalidate it.


>From http://xmlgraphics.apache.org/fop/0.94/graphics.html :
===============

FOP caches images between runs. There is one cache per FopFactory instance.
The URI is used as a key to identify images which means that when a
particular URI appears again, the image is taken from the cache. If you have
a servlet that generates a different image each time it is called with the
same URL you need to use a constantly changing dummy parameter on the URL to
avoid caching.

The image cache has been improved considerably in the redesigned code.
Therefore, a resetCache() method like in earlier versions of FOP has become
unnecessary. If you still experience OutOfMemoryErrors, please notify us.
===============

so when i change resources/skins/default/xslt/document-to-xslfo.xsl
  <xsl:template name="insertGraphic">
    <fo:external-graphic src="url('{@src}">
    ....

to

   <fo:external-graphic src="url('{@src}?test123">

then i'm getting the new image in my PDF, neat!

random() or now() don't seem to be supported in standard xslt though, so
perhaps there is some random-enough data available elsewhere in the document
that we can append to the URL each time? Should this be made the default
behaviour also you think ? Other than performance (impact to be determined)
I don't see any reason for FOP to maintain a separate image cache.

On Wed, 2008-03-12 at 12:04 +0100, Karel Vervaeke wrote:
> > Restarting the wiki should obviously help, but that is equally obviously
> > not a solution ;-)
> >
>

We could restart it overnight but indeed it seems a bit harsh :)


>
> > Not that it matters, but are you sure the last version is published etc?
>

Yep that's the case.

Thanks,
Jorg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.cocoondev.org/pipermail/daisy/attachments/20080312/46147aa5/attachment.htm