Hello, Thomas you said its not a good idea to release the ProtectedStream reference. This is clear, because of the ImageTagRegistry#readUrl when sre.handleStream(is, purl, needRawData); is called. Then the PNGRegistryEntry is used, where a Thread creates the Image. But what about calling is.close(); => I would call in ProtectedStream#close the release method ? Is there any reason of doing nothing in the close method of ProtectedStream ? I mean otherwise the is must be casted to ProtectedStream and calls release.
________________________________ Von: Kerschbaum Michael [mailto:[email protected]] Gesendet: Mittwoch, 08. Juli 2009 10:25 An: [email protected] Betreff: Images in Batik kept open... Hello, I have the problem, that when a svg has an image via xlink, this image can't be deleteted or renamed, removed any more after the svg was loaded. And the image is still locked after the svg document was disposed. I have found a problem report for that ...svg:image - referred images kept open?... but there was no solution posted. Is there a solution or a workaround ? The Problem is, that my application views svgs with png images. The svg's and png's stored on an samba share, and a nother application updates them. This application is not able to put the png file to the share ? Clean up the image and svg cache in batik didn't help. mfg Michael
