Jim Cheesman wrote:
> I have to back this statement up - jar reloading on TC4/Win2000 is a risky
> business, to say the least. Sometimes it works, sometimes not... I wonder
> if it's anything to do with the server checking for a new jar at the same
> time as the filesystem overwrites the old one?
Nasty. Maybe it's a JDK for Win specific thingy, rather then a Tomcat
bug? Does it work with IBM JDK?
I'm having some problems with jar reloading in TC 3.3. But this is
happening on Linux and the tricky part is that DependManager doesn't
even report jar files as dependencies...
Bojan
