> I had this problem also. The only way I could get Tomcat 4 to update was to > decompress the war into a directory in webapps. Then I use the manager to > reload my application. It's all in an ant task, which makes it not very > painful: Thanks a lot for the idea.
> I no longer use Tomcat 4 due to stability issues, I'm using > jboss/tomcat3.2.3 bundle which handles hot deployment beautifully. The But supports old API only:( The question to tomcat team: is it registered bug/problem? What are perspectives? Does all this mean Tomcat 4.0.1 is not ready yet for servlet development environment (only for production:)? Cheers, Sergey -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
