> -----Ursprüngliche Nachricht----- > Von: Andreas Delmelle [mailto:[EMAIL PROTECTED] > Gesendet: Freitag, 6. Juni 2008 11:11 > An: fop-users@xmlgraphics.apache.org > Betreff: Re: Picture update problem > > On Jun 6, 2008, at 10:43, Antti Karanta wrote: > > Hi > > > I have an issue that I think is due to FOP caching images. The > > situation is this: > > > > * FOP is embedded in our software. I create a single FopFactory and > > create a new FOP instance via it for each render. > > * I render a pdf with fo that references some svg image files. It > > comes out fine. > > * Some of the svg image files are updated on the hard drive. > > * I render a pdf again (w/ the same name, new FOP instance > though, but > > created via the same fop factory instance). The image that has been > > changed on disk appears as it was before it was updated. > > Indeed. If the URI for the image is the same in both cases, > then the second time, the image will be fetched from the > cache. The ImageCache itself is no longer part of FOP, but > resides in XMLGraphics Commons now. > > Unfortunately, AFAIK, we still have no way of signal to the > image- loading framework that a particular image must not be cached. > > One possible solution would be to do the following, after > rendering the document the first time: > > org.apache.xmlgraphics.commons.image.loader.cache.ImageCache.c > learCache( > );
I do reuse the FopFactory, too. But ImageCache.clearCache() is not static!? At least in xmlgraphics-commons-1.4svn.jar in FOP TRUNK. What should we do? Not reusing the FopFactory? Greetings, Ingo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
