:) I got a good laugh out of your response Christopher and I appreciate you taking the time to guide a possibly astray developer but let me hopefully put your mind somewhat at ease in regards to our development practices/environment. Not claiming we have anything resembling a perfect process either. We have a separate department that is more marketing/static content than it is anything, they'll put their own stuff up on the website that for the most part is not under revision control, but backed up and they each have their own local copies, heavy dreamweaver users and we'll give them tag libraries to use for some dynamic content here and there. All our tag libraries, main web workflows (ecommerce), search functionality, page templates etc. are under revision control, we are happy subversion users after escaping from starteam some time ago. Our classes, web.xml, libs are deployed in one war file for our main site, deployment configuration *managed by JDeveloper project, I'm not proud of this but we are migrating off of Oracle app server and I plan to take a look at Eclipse for ide and change our project builds to use maven or ant. We have other traditional web apps whose content/config/classes/libs are all traditionally packed up and deployed in a war.
As for my previous problem separating config/lib/classes from content. I ended up using a symlink on WEB-INF directory on ROOT context, I've got app called foo, ROOT/WEB-INF is symlinked to FOO's WEB-INF directory. I can redeploy FOO and ROOT gets new config/classes/lib via symlink and I don't have to worry about docBase of ROOT getting undeployed. Tried aliases context attribute in 7.0, just couldn't get it to provide same separation symlink did, or I just wasn't using it correctly. Jason >> I would have to resort to hand copying in >> class file/config and lib changes into the WEB-INF so as not to risk losing >> any content files on a redeployment. > > This also sounds completely insane. > > You need to have a sane deployment process. Generally, when developing a > web application, you can feel free to have all your .java files, .jsps, > static content, etc. scattered all over the place. Once it's time to > deploy, though, it's time to sew everything up into a WAR (whether it's > actually a .war file or just on the disk with the same directory/file > structure). I highly recommend using Apache ant for this sort of thing: > there's a <war> "command" that you can use where you can specify all the > places where source files should come from. Boom: instant .war file. > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
