Noel J. Bergman wrote:
Stephen,
It a JNDI ObjectFactory that lets you access a new instance of the
Merlin Kernel from a JNDI context.
Context initCtx = new InitialContext();
Context envCtx = (Context) initCtx.lookup("java:comp/env");
Kenel kernel = envCtx.lookup("merlin/ServiceFactory");
Naturally this needs to be backed by a JNDI resource declaration as
per the Servlet 2.3 spec (or alternative JNDI configuration). That's
where parameters such as the Merlin system and block definition URLs
are declared.
Do you have any interest in seeing org.apache.naming moved out of Tomcat
into a common project for others, e.g., Avalon, James, and others, to use?
Yes.
I spend some time going over the Tomcat code partly to get a validation of the Merlin/JNDI connection up and running inside tomcat but also because of the related discussions on this topic over on the James list. While I don't have a real deep grip on the content of the org.apche.naming package - I do have the impression that this may be a starting point for the addition of handlers support service URLs.
Cheers, Steve.
--- Noel
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
