This is the solution I have for hackyDevSite hotdeply on tomcat 5.5:
1. Manually put this file under tomcat/conf/localhost/cataline
<?xml version='1.0' encoding='utf-8'?>
<Context docBase="/E:/work-csdl/hackyDevSite/webapp/" path="/hackyDevSite">
</Context>
2. When you want to do redeployment, do
ant webstop clean compile webstart
Basically, it stops hackyDevSite web application (but not removing it)
and then starts it. If there is any change in java file or jsp file, the
change will be reflected after restarting the web applications.
Cheers,
Cedric
(Cedric) Qin ZHANG wrote:
1. I have updated hackyDevSite to JSP2.0 and JSTL 1.2, and deleted a
bunch of jar files. Hackydev site now works with Java 5 and Tomcat
5.0/5.5. I am not going to support java 1.4 and Tomcat 4.x.
2. I have taken out structs completely from hackyDevSite.
The only function hackyDevSite needs from structs is the controller,
and it make no use of Stuct's tag library. It quite easy of hand roll
my own controller. Structs is not a java standard, and has been dead
for more than one year though its website tries to deny the fact by
saying we would continue to develop it and make it compatible with
JSF. One thing I learned from Hackystat evolution is that the less
your application depends on non-standard third party libraries, the
less maintenance hassle it will have.
3. The tomcat 5.5 hot-deployment copy-over problem is still not
solved. It's true that we can put a configuration file under tomcat
conf directory:
<?xml version='1.0' encoding='utf-8'?>
<Context docBase="/E:/work-csdl/hackyDevSite/webapp/"
path="/hackyDevSite">
</Context>
But when you undeploy the application, the file will be deleted. Next
time you do hot deployment, tomcat starts copy everything again.
I'll do some googling tomorrow to see if there is a way out.
Cheers,
Cedric
Hongbing Kou wrote:
Cool, I think we can change it. One thing I found is that
deploy/undeploy are also
supported by Tomcat 5.0.x release. I think this change will allow to
deploy on both
versions.
At 02:22 PM 11/29/2005, Philip Johnson wrote:
--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
