OK, this seems to work. I replaced the line in my test and it behaved like I expected. I'm working on upgrading to the latest version and integrating it with my code.
Thanks for checking this out. Michael Bishop -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Saturday, November 04, 2006 3:32 PM To: [email protected] Cc: [email protected] Subject: RE: Resolving xlink:href at a later time? Hi Michael, "Bishop, Michael W. CONTR J9C880" <[EMAIL PROTECTED]> wrote on 10/23/2006 10:48:45 AM: > OK, this is becoming an issue I can't solve. Since I can't pull the URL > off the cache, I decided to clear the cache: > > URLImageCache.getDefaultCache().flush(); Sorry about this, it turns out that batik.ext.awt.image.spi.ImageTagRegistry has it's own 'internal' caches for images. So if you replace the above line with: ImageTagRegistry.getRegistry().flushCache(); Things will work. I also just added a method: ImageTagRegistry.flushImage(ParsedURL purl) that allows you to flush the cache of one image. I am sorry that I didn't remember/realize that Batik doesn't use the URLImageCache default cache for images any more... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
