http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jetty/
Drill down to Jetty/extra/plus/src/org/mortbay/jndi. There are 7 classes:
org.mortbay.jndi: InitialContextFactory - implementation of the JNDI InitialContextFactory interface
ContextFactory
- an ObjectFactory for Contexts. Used to bind
a Context by a classloader NamingContext
- implementation of the in-memory context mappings Util
- handy naming methodsorg.mortbay.jndi.java:
javaNameParser
- the JNDI NameParser for java: namespace javaRootURLContext
- root of the java: namespace javaURLContextFactory
- URL context factory for java: URLsThese are sufficient to run an in-memory provider for the java: namespace with shielded java:comp/env contexts per application and supporting binding of LinkRefs, References, Referenceables and Serializables.
On the plus side for Tomcat, I think that as the Jetty JNDI code is relatively more recent than the Tomcat JNDI code, I'd assume that the Tomcat one is probably more field tested. However, on the other hand, the Jetty JNDI code is smaller and simpler (well, it is to me at least, but then again, I wrote it ;-) ).
Jan --
/**************************************** * Jan Bartel <[EMAIL PROTECTED]> * Associate * Core Developers Network LLC * http://www.coredevelopers.net ****************************************/
