Hi, I think JNDI resources have to be associated with an actual context explicitly, to avoid creating multiple copies. I'm not a big fan of DefaultContext anyways.
Yoav Shapira Millennium Research Informatics >-----Original Message----- >From: Sandy McArthur [mailto:[EMAIL PROTECTED] >Sent: Wednesday, April 07, 2004 4:19 PM >To: Tomcat Users List >Subject: Re: Filter.init and DefaultContext JNDI resources > >After further testing on my using a JNDI resource in the >Filter.init(...) method I found that if I use a DefaultContext to link >a resource it fails. eg: > ><DefaultContext> > <ResourceLink name="jdbc/test" global="jdbc/db" >type="javax.sql.DataSource"/> ></DefaultContext> > >But if I link the resource in a Context I can load a JNDI resource in >my Filter's init(...) method. eg: > ><Context path="/JNDI" docBase="JNDI.war"> > <ResourceLink name="jdbc/test" global="jdbc/db" >type="javax.sql.DataSource"/> ></Context> > > >In both forms of resource linking above the Filter can load the JNDI >resource from the doFilter(...) method. > >Any reasons that there should be a difference in behavior for a >ResourceLink depending on if you link it in a DefaultContext or a >Context? > >Sandy 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]
