Interesting. It's actually what I meant earlier, although I expressed it badly.
So, I am currently including my webapp's <Context> in conf/Catalina/localhost/mywebapp.xml, which is sub-optimal for 2 reasons: 1. it's outside the webapp directory 2. the path depends on the server configuration - not predictable It seems that it would be neater if the context xml file were within the webapp directory. Is there a reason why it is in fact read from conf/Catalina/localhost at atartup? Why not from within a defined location in each webapp? PS the reason I don't use wars is that while developing, I can't see the point in packaging a war up after every change, only then to unpack it when I restart TC. Might as well change the files directly. PS what does TC do with the context.xml file when it reads it from a war, does it copy it somewhere? > -----Original Message----- > From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > Sent: Tuesday 26 October 2004 17:48 > To: Tomcat Users List > Subject: RE: JNDI DataSource GlobalResources problem > > > > Hi, > Nope, if you just use the unpacked directory structures to deploy, > META-INF/context.xml will not be read. > > Yoav Shapira http://www.yoavshapira.com > > > >-----Original Message----- > >From: Steve Kirk [mailto:[EMAIL PROTECTED] > >Sent: Tuesday, October 26, 2004 12:46 PM > >To: 'Tomcat Users List' > >Subject: RE: JNDI DataSource GlobalResources problem > > > > > >> >All I did was move my context config file from > >> > conf/Catalina/localhost/mywebapp.xml > >> >to > >> > webapps/mywebapp/META-INF/context.xml > >> > > >> >is there something I've missed? > >> > >> Yeah. The META-INF/context.xml is consulted when deploying a > >> WAR. Just > >> putting it there for an already deployed and expanded WAR > >> won't do much > >> of anything. > > > >OK thanks. > > > >I should have said, I don't use war files, I just store files under > >webapps/mywebapp in the file system. Will my context.xml > ever be read, > >e.g. > >when TC is restarted? This is what I meant above when I said that I > >thought > >that context.xml is only useful when using the "deploy" > feature (which > I > >don't use). > > > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > This e-mail, including any attachments, is a confidential > business communication, and may contain information that is > confidential, proprietary and/or privileged. This e-mail is > intended only for the individual(s) to whom it is addressed, > and may not be saved, copied, printed, disclosed or used by > anyone else. If you are not the(an) intended recipient, > please immediately delete this e-mail from your computer > system and notify the sender. Thank you. > > > --------------------------------------------------------------------- > 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]
