The other thing to note about reloading JSPs is that tomcat 5.5 seems
to copy ones web context directory into its own webapps directory.
Any changes to the original JSPs will not show up unless you
physically copy the JSP from the original directory to the webapps
directory.
I haven't observed this behavior with my Tomcat 5.5.
Maybe you have set antiResourceLocking="true" or something like this.
In this case I think tomcat will copy all the files.
I double checked and antiResourceLocking is false. Is there some other
configuration property somewhere that would indicate that the webapp is
to be copied? I use the 5.5.9 tomcat for Linux pretty much right out of
the box.
-Trav
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
