So far I don't see much I like. If the JSP developer uploads right to the webapp then my web resources are out of sync. That means if I make a tweak to the JSP the next time he uploads, poof. That is damn ugly.
The best scenario is as follows. There is a single CVS repository. I have tomcat (or whatever) running and he does too. We both checkout the original source. He messes with the JSPs, reloads he local app, get's it all tweaked. Then, he CVS commits all changes. I do the same. At the end of the day, week or whatever interval, the CVS version is checked out into a war file and deployed. The last step is the only tricky part, I will have to make an ant script for that. This brings me to my next question, which may be container specific. Don't let this throw off the topic of the post, maybe a quick little reponse. If I copy over a new version of the *.war file for an app, why doesn't the container redeploy it over the old version? It seems like once a war has been deployed, you have to nix the whole folder, restart the container and copy in the new war. It would seem to me the container should check the timestamp of the war against the folder or something and if it is newer, redeploy it. This also causes issues with files that were removed from the war, which are now trash files and left in the deployed app. Dan -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Daniel Allen, <[EMAIL PROTECTED]> http://www.mojavelinux.com/ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - "The package said 'Windows 95 or better', so I installed Linux" - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
