What you are suggesting doesn't sound very safe without using a source code control system.
What we do is to have each developer have a local copy of Tomcat on their PC, with their own copy of the source code for the web app. That copy is a sandbox, copied out of the master project in the source code control system (MKS Source Integrity). When they want to edit a file, they check it out to their sandbox, work on it, then check it back in to the main project. > ---------- > From: Anthony Smith[SMTP:[EMAIL PROTECTED]] > Reply To: Tomcat Users List > Sent: Monday, September 30, 2002 5:10 PM > To: Tomcat Users List > Subject: web.xml help > > Let me explain my problem just in case there is another solution... > > In my Tomcat enviroment, there may be several developers working on one > webapp, but I want each one of the developers to use their own web.xml or > some variant of it. Is this possible? > > So for developer 1's folder he can drop his xml file in the WEB-INF folder > and have access to all its properties, but still have access to web.xml as > well as the other xml files that may be in existence... > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
