> Hi: > > Are you creating the ".WAR" on one machine then copying it to a server on > another machine? If so, then check that the clocks on the two machines are > set to the same time. I've had problems where my compile-machine's clock > was running a little slow, which made the ".WAR" file appear to be older > than the already-unpacked directory. In this case, Tomcat figures you've > modified the existing directory, so it doesn't unpack the new one. > > Greg Trasuk, President > StratusCom Manufacturing Systems Inc. - We use information technology to > solve business problems on your plant floor. > http://stratuscom.ca
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. I'm not 100% sure, but I don't think that file based JAR URLs have that problem. Remy
