> I think it's a JDK bug. Since the WAR will be opened through a JAR URL, it > is cached by the JDK until the JVM is terminated. I tried everything (since > it caused another problem), but there's no workaround unless you make the > URLs strings different. Cool! OK, I'll try IBM's JDK.
> I'm not 100% sure, but I don't think that file based JAR URLs have that > problem. I use the jar:file://... url. Do you say that I have to unpack my WAR before deploying? Regards, Sergey
