Hi Joaquim,
I think you always should do a COMPLETE release of the war file.
So you always have an atomic, conistent relase.
When it comes to rollback, versioning etc. you're much better off in having
a complete release as war file.
You can use hot deployment, so when you copy the new war file across, it's
automatically deployed and you don't loose your sessions.
However, my experiences with hot deployment are terrible, it was not working
stable at all, I had many application crashes caused by hot deployment.
So what I do now is build a war file, rename it as zip file and unzip it
manually, they reload the application, it's somehow stuid, but working
stable.
Cheers
Bernhard
> -Ursprüngliche Nachricht-
> Von: Insyde [mailto:[EMAIL PROTECTED]
> Gesendet: Montag, 18. Juli 2005 19:47
> An: Tomcat Users List
> Betreff: Deployment using WAR files
>
>
> Hello,
>
> I have some questions about many people working in the same
> project and deploying using WAR file.
>
> I belong to a group that is developping a web application and
> use TOMCAT to test it. At the beginning the deployment was
> done by copying classes, jsp, and jar files etc to the folder
> of our web application into webapps subdirectory of TOMCAT.
> Then we decided to use a WAR file. However there are many
> people working in the same web application and deployment
> using a WAR means to undeploy and deploy the whole web
> application. We thought that one possible solution could be
> to copy the components of web application to the folder of
> web application as we used to do. But is that the correct way
> to do it ? How to could we deploy part of a web application
> using war files ? Is it possible to do it ? We wonder how
> people work in order to solve or minimize this situation.
>
> Thanks in advance for any help.
>
> Joaquim Roberto.
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
