Mark 6.0.18 **does** unpack a foo#bar.war to a foo#bar directory
as long as you have enough disk space ( woops ;) interestingly no error message to tell you if the unpack failed tho'.... I'm havng a little bit of trouble picking up local resources in my app deployed as foo#bar, using the ClassLoader, - but I'm sure I can fix this as the ClassLoader is picking up bundled libraries OK thanks again Trevor Paterson PhD new email [EMAIL PROTECTED] > -----Original Message----- > From: Mark Thomas [mailto:[EMAIL PROTECTED] > Sent: 25 August 2008 17:37 > To: Tomcat Users List > Subject: Re: Tomcat6 relative contexts > > trevor paterson (RI) wrote: > > excellent thanks Mark - I changed to build 18 and > foo#bar.war deploys > > to context /foo/bar > > > > it doesn't seem to unpack? there may be a good reason for this?? > > It should. There is some work on my todo list in that area. > I'll add checking this to that list. > > Mark > > > > > Trevor Paterson PhD > > new email [EMAIL PROTECTED] > > > > Bioinformatics > > The Roslin Institute > > Edinburgh University > > Scotland EH25 9PS > > phone +44 (0)131 5274477 > > http://www.roslin.ed.ac.uk > > http://www.comparagrid.org > > http://www.thearkdb.org > > > > Please consider the environment before printing this e-mail > > > > The University of Edinburgh is a charitable body, registered in > > Scotland with registration number SC005336 Disclaimer:This > e-mail and > > any attachments are confidential and intended solely for the use of > > the recipient(s) to whom they are addressed. If you have > received it > > in error, please destroy all copies and inform the sender. > > > > > > > >> -----Original Message----- > >> From: Mark Thomas [mailto:[EMAIL PROTECTED] > >> Sent: 25 August 2008 16:45 > >> To: Tomcat Users List > >> Subject: Re: Tomcat6 relative contexts > >> > >> trevor paterson (RI) wrote: > >>> Prior to tomcat6 you could happily deploy a 'bar.war' to > a context > >>> like '/foo/bar' simply by including a context.xml file in > >> the META-INF > >>> directory of the war > >>> > >>> with content <Context path='/foo/bar'/>. > >> Actually, that won't quite have done what you think it did. > >> You normally would have ended up with double deployment. > >> > >>> we can no longer get this to work - the only way we can get a > >>> subcontext recognized is by putting this Context element in the > >>> server.xml (which then causes autodeployment to both '/bar' > >> and '/foo/bar'). > >>> > >>> We have tried using the TomcatClientDeployer aswell as > deploying on > >>> start up and through the web interface to manager to no avail > >>> > >>> are we missing some subtle change from tomcat5 to 6 that > is causing > >>> this? > >> As of 6.0.18, you have a couple of options: > >> 1. Deploy the war outside the appBase and use a > foo#bar.xml context > >> file 2. Name your war foo#bar.war 3. Deploy using a > directory foo#bar > >> > >> 2 & 3 only work in 6.0.18 onwards > >> > >> See > >> http://tomcat.apache.org/tomcat-6.0-doc/config/context.html > >> for details > >> > >> Mark > >> > >> > >> > >> > --------------------------------------------------------------------- > >> To start a new topic, e-mail: users@tomcat.apache.org To > unsubscribe, > >> e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > > --------------------------------------------------------------------- > > To start a new topic, e-mail: users@tomcat.apache.org To > unsubscribe, > > e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org To > unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
