--On Tuesday, November 29, 2005 12:22 PM -1000 Hongbing Kou <[EMAIL PROTECTED]>
wrote:
Hi, Philip & Cedric,
I stopped at these two threads. I am not sure whether antiJarLocking works or
not
to hackyDevSite under Tomcat 5.5
http://issues.apache.org/bugzilla/show_bug.cgi?id=10026
http://www.mail-archive.com/[email protected]/msg153040.html
It seems that there is no way to disable the war folder copy.
I do not think you are correct. Here's some additional info:
- The links cited above question whether you can hotDeploy/undeploy in Tomcat 5.5. I've
been hotDeploying and hotUndeploying hackystat using Tomcat 5.5.12 all morning, and
watching the hackystat folder disappear from and reappear into the webapps directory. So
far, Hackystat seems to be OK under 5.5.12. The only major issue I've discovered under
5.5.12 is that you need to do a deploySoap even for a quickStart, which didn't use to be
true in Tomcat 4. So, I'll add that target to quickStart, which I know will make a few
people happy. :-)
- Yesterday, I had a problem with hackyDevSite not undeploying completely (i.e. not
completely deleting the <tomcat>/webapps/hackydevsite folder). The problem was that
struts.jar was not being deleted. In reading through the above links that Hongbing
supplied, I noticed that one workaround posted was to expand the struts.jar into
WEB-INF/classes and then delete the jar file. I just tried that, and now hackyDevSite
can undeploy just fine.
- I believe that if we supply a context configuration XML file, and provide a "docBase"
attribute, then we can deploy/undeploy without copying under Tomcat 5.5. The following
link takes you to the "Deploy a new application from a local path" section, then scroll
down to "Deploy using a configuration XML file":
<http://tomcat.apache.org/tomcat-5.5-doc/manager-howto.html#Deploy%20A%20New%20Application%20from%20a%20Local%20Path>
The following link documents the context configuration file, and the docBase
attribute:
<http://tomcat.apache.org/tomcat-5.5-doc/config/context.html>
Cheers,
Philip
