Hey
I was wondering about the possibility to update a deployed jar without
having to copy it upon deploy. I digged into the JDK, especially
URLClassLoader, and even specified my own URLStreamHandlers which did
not lock files and all, only to find an "optimization" in the JDK loader
code that bypasses all that for file: URL's. Go figure.
However, it might be possible if we loaded the jar from /deploy through
HTTP (I know I know, silly). Then the normal JDK caching stuff would be
used, and the file itself wouldn't become locked. This way we wouldn't
have to deal with the caching ourselves.
Comments?
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
