Rickard,
Did you set the URL to be something like "jar:file://myfile.jar"? I am
working on exactly this sort of thing (to show load progress for a
commercial application) and it is working fine for me. I subclassed
URLClassLoader to ensure the URL I created had the jar: on it.
----- Original Message -----
From: "Rickard �berg" <[EMAIL PROTECTED]>
To: "jBoss Developer" <[EMAIL PROTECTED]>
Sent: Friday, August 18, 2000 4:18 AM
Subject: [jBoss-Dev] Ah well
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
-------------------------------------------------------------------------
This email server is running an evaluation copy of the MailShield anti-
spam software. Please contact your email administrator if you have any
questions about this message. MailShield product info: www.mailshield.com
-------------------------------------------------------------------------
This email server is running an evaluation copy of the MailShield anti-
spam software. Please contact your email administrator if you have any
questions about this message. MailShield product info: www.mailshield.com
