Note that "context.xml" is only applicable when you are using the "deploy" task for the manager app (and note that this can only be invoked via the Ant catalina manager tasks because browsers don't support HTTP PUT). If you are putting a context configuration file in the webapps directory for deploying a .war file or a directory relative to (or inside) the webapps directory, then name the file anything you want. I would recommend, however, that you name the file the same as you named the .war file or directory you are deploying. This makes it easier to know, at a glance, which context configuration file is for which app.
Actually, as part of the deploy process, Tomcat looks for the META-INF/context.xml file inside your .war file and extracts that to a file named the same as the .war file, less the .war extension.
So, if you have...
myapp.war
Then META-INF/context.xml gets extracted (in the same directory where the .war file exists) to...
myapp.xml
Hope that clears things up.
Jake
At 04:51 PM 3/21/2003 +0000, you wrote:
* Collins, Jim <[EMAIL PROTECTED]> [0340 16:40]: > Hi Jake, > > Thanks for getting back so quick. So the context file in META-INF should be > context.xml and not myapp.xml? > > That is maybe where I have been going wrong, I read some previous posts on > this from Craig and I thought he said you name the context file with the > name of your app and a .xml extension.
I've done that before now, when I've needed to add contexts without editing server.xml - BUT those files have gone into the webapps directory (where a warfile would normally go) - see manager.xml which I think is in webapps/ by default. This context.xml method sounds like a safer solution though...
-- He's the kind of man for the times that need the kind of man he is ... Rasputin :: Jack of All Trades - Master of Nuns
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
