yes context.xml is fine in META-INF. in fact it is preferred over having it in server.xml. your alternative is to put it in conf/enginename/hostname/yourwebappname.xml (which is in fact what TC will do for you when it unpacks the war).
I don't know that you can have the context path name different to the war file. I'm not 100% sure, but can't see how to do it. in fact I can see it being a source of potential confusion. can you explain why you want to do that? > OK, I am totally confused. Is or is it not best practice to provide a > context.xml in META-INF. I thought this was required for hot > deployment > to work. If I want my context path to have a different name to my war > file, how do I achieve this? > > thank you > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
