> there seems to be a number of ways to achieve the per-mailet context thing.
It you want, take a look at org.apache.naming (under the tomcat project). I think that you'll find that per-mailet would be a real complication, and not necessarily desireable. In Tomcat, the Servlet Specification specifies that resources are per-webapp, and each webapp has its own classloader. ref: http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-4.0/catalina/src/share/org/ apache/naming/ There is another copy elsewhere, part of the TC5 CVS structure, but the one above may be the better place to start for now. We can ask Remy for advice. Actually, if we decide to adopt JNDI, I'll ask Remy if he could help us out a bit (org.apache.naming is under Tomcat, but is supposed to be independent, and available for all projects that might want it). > > Servlets don't see separate contexts, and that is the > > model closest to the Mailet API. > As far as I am aware, servlets have nothing to do with JNDI. > Is this a recent addition to the servlet spec? See Servlet Specification v2.3 sections 9.11, 13.3 and A.2. --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
