James Lewis wrote:
always perform such a lookup successfully, but when I try from a
ContextListener contextInitialized method it fails: the same code WILL
NOT FAIL contextDestroyed !!!
Hmmm, odd. This is *exactly* what I do pretty much. I have a
LifeCycleListener specified in the webapps//WEB
Tomcat Users List
>Subject: RE: [tomcat] RE: JNDI datasource non available in
>ServletContextListener.contextInitialized
>
>> always perform such a lookup successfully, but when I try from a
>> ContextListener contextInitialized method it fails: the same code
WILL
>> NOT FAI
> always perform such a lookup successfully, but when I try from a
> ContextListener contextInitialized method it fails: the same code WILL
> NOT FAIL contextDestroyed !!!
Hmmm, odd. This is *exactly* what I do pretty much. I have a
LifeCycleListener specified in the webapps//WEB-INF/web.xml like
James Lewis wrote:
- define the resource in server.xml (this is a little 'limitating' for me)
- deploy the applications in unpacked format (i.e. not from a war file:
this is quite limiting, however)
Yep, not good to stick them in server.xml.
Your .xml file containing your resources should
- define the resource in server.xml (this is a little 'limitating' for me)
> - deploy the applications in unpacked format (i.e. not from a war file:
> this is quite limiting, however)
Yep, not good to stick them in server.xml.
Your .xml file containing your resources should be in the
webapps/ dir
