Noel J. Bergman wrote:
I agree that per-mailet contexts are very difficult, and wouldn't want to take this to the degree Aaron has with having everything function through JNDI.there seems to be a number of ways to achieve the per-mailet contextthing.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).
The more I've thought about it, the more I like using JNDI for generic resources. Basically we can rely on the J2EE spec on how to do this, just as the servlet API does so. This would give a standard way to have access to logging, datasource, advanced app configuration, and other resources via JNDI.
I agree with Stephen that the servlet API is perfect, but I do think it did achieve a good balance of simplicity vs. complexity and gives people a level of familiarity when getting into mailets.
--
Serge Knystautas
President
Lokitech >> software . strategy . design >> http://www.lokitech.com/
p. 1.301.656.5501
e. [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
