Take a look at http://issues.apache.org/bugzilla/show_bug.cgi?id=10026. It may
be related.
Mark
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Saturday, October 08, 2005 5:20 PM
To: tomcat-user@jakarta.apache.org
Subject: hot redeploy now work. locked
I am confused. It looks like they found a way to make tomcat so if the
jars had that problem, tomcat could still handle it, but only put this in
4.x. It is not in 5.0(ie. the last post in the message).
The weird thing is a friend had the same version but not the same problem.
I upgraded my jvm
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
I am confused. It looks like they found a way to make tomcat
so if the
jars had that problem, tomcat could still handle it, but only
put this in
4.x. It is not in 5.0(ie. the last post in the message).
The functionality has been in
