I like this approach, using "setUseCaches" on each URLConnection, because it limits the setting to the URL object in question, and that way HiveMind will not go changing a vm-wide property that may affect other applications.
I chose "setDefaultUseCaches" myself because that way I can avoid modifying HiveMind, and it works for all the other 20 or so jars I am using! :-) It would probably be a good idea to profile this change in order to test for any performance hit the change may cause. Jim Achim Hügen wrote: > > I would suggest to fix it in all places where urls are used for opening > a stream. That wouldn't limit the patch to web applications. > > As far as I understand we must modify the code > in XMLResourceProcessor, MessageFinderImpl, and URLResource. > Before: > > URL url = resource.getResourceURL(); > return new InputSource(url.getInputStream()); > > After: > URL url = resource.getResourceURL(); > URLConnection conn = url.openConnection(); > conn.setUseCaches(false); > return new InputSource(conn.getInputStream()); > > Achim > -- View this message in context: http://www.nabble.com/HiveMind-1.1.1---jar-locking---XMLResourceProcessor-tf2735127.html#a7648169 Sent from the Hivemind - User mailing list archive at Nabble.com.
