Original Message-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 31, 2006 8:55 PM
To: Tomcat Users List
Subject: RE: RE: context.xml
> From: Klotz Jr, Dennis [mailto:[EMAIL PROTECTED]
> Subject: RE: RE: context.xml
>
> I am hoping to find a place for a c
other reason we
couldn't do this is because the admin doesn't allow for setting the
defaultCatalog property of a connection pool.
Tim
-Original Message-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 31, 2006 8:55 PM
To: Tomcat Users List
Subject: RE: RE: co
> From: Klotz Jr, Dennis [mailto:[EMAIL PROTECTED]
> Subject: RE: RE: context.xml
>
> I am hoping to find a place for a context.xml to live where it will
> never get deleted. That a customer can change and when we give them a
> new war file, the context.xml changes that they ha
>
> From: "Klotz Jr, Dennis" <[EMAIL PROTECTED]>
> Date: 2006/01/31 Tue AM 08:01:01 EST
> To: "Tomcat Users List"
> Subject: RE: RE: context.xml
>
> Thanks again Warren.
>
> I guess I must be approaching this from the wrong perspective o
changes that they have made will stick
around.
Is there a way to do this that you know of?
-Dennis
-Original Message-
From: Warren Pace [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 31, 2006 5:19 AM
To: Tomcat Users List
Subject: Re: RE: context.xml
>
> From: "Klotz
>
> From: "Klotz Jr, Dennis" <[EMAIL PROTECTED]>
> Date: 2006/01/30 Mon PM 08:28:10 EST
> To: "Tomcat Users List"
> Subject: RE: context.xml
>
> Thanks Warren for the reply.
>
> Wouldn't that version of the file be deleted when I undeploy?
>
If you're using the manager app to "un-deploy" the