Webapps shouldn't need to implement these two work arounds. It would be nicer if the webapp could somehow tell fop which images are dynamic and shouldn't be cached. Maybe fop's userconfig.xml could include patterns for image URLs to be included and/or excluded from the cache.
Well, certainly. Its not a new thought however, and it opens a can of worms you probably aren't aware of yet. Check https://sourceforge.net/mailarchive/forum.php?thread_id=1395669&forum_id=14047 https://sourceforge.net/mailarchive/forum.php?thread_id=1398613&forum_id=14047
I'm about to try another work around, that is to include the image as inline svg with <fo:instream-foreign-object> and thus avoid unwanted caching.
Clever.
J.Pietschmann
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
