> From: Christopher Schultz [mailto:ch...@christopherschultz.net] > Subject: Re: Can a JNDI resource be in a webapp's lib folder > > I think this is a reasonable desire, and I'm not sure why Tomcat's > architecture does not allow this. Honestly, using the webapp's > ClassLoader to create JNDI resources would make a lot of sense and fix > at least one long-standing bug/resource leak when restarting webapps.
Not sure if that's feasible without spec changes. The JNDI registry is for the entire JVM; if resources reachable through it were under control of a webapp classloader, they would be visible to but not usable by other webapps. There may be ways to construct local (per-webapp) JNDI domains, but I don't think there's anything like that in the spec. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
