Interesting.  So, what If I wanted to deploy an app as a .war file with a
context.xml file in META-INF, but wanted the app to be deployed to
webapps/dir1/dir2/myapp rather than just webapps/myapp?  The file in META-INF
must be named "context.xml".  What clue can one give Tomcat the clue that it
should be deployed in a special way other than manually creating the context
config file manually before deploying the app?


Jake

Quoting David Boyer <[EMAIL PROTECTED]>:

> Yep, that's it. I'd already tried underscore (and everything else except
> #).
>
> Thanks!
>
> >>> [EMAIL PROTECTED] 3/3/2005 6:14:35 PM >>>
>
> Yes there is. I cannot remember, but it is in the archives. It has to
> do
> with how you name the file. Something like dir1#dir2#appname.xml or it
> may
> have been an underscore. I will see if I can find it if no one else
> knows
> off the top.
>
> Doug
>
> ----- Original Message -----
> From: "David Boyer" <[EMAIL PROTECTED]>
> To: <[email protected]>
> Sent: Thursday, March 03, 2005 5:31 PM
> Subject: path attributes in context xml files
>
>
> >I use xml files in /conf/[enginename]/[hostname] to define my
> contexts.
> > I now know that Tomcat 5.5.x doesn't allow for 'path' attributes in
> the
> > Context elements when defined that way.
> >
> > Previously, I could specify the path as '/dir1/dir2/appname'.  I can
> > easily rename the xml file to 'appname.xml', but how do I get the
> other
> > directories into the path without a 'path' attribute in the Context
> > element. Using the 5.5.x approach, by web application is at
> '/appname'
> > instead of '/dir1/dir2/appname'.
> >
> > Is there a way to get a multi-directory path using this approach (a
> la
> > Tomcat 5.0.x), or will I need to declare these Contexts in my
> server.xml
> > to do that?
> >
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to