Leo Simons wrote:
what does this do?
It a JNDI ObjectFactory that lets you access a new instance of the
Merlin Kernel from a JNDI context.
For example, a servlet could do the following:
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.
I would like to change (or set up) informal sandbox policy: before
you put a new subproject in sandbox, write up a short proposal for
the subproject, so everyone knows the project is there and what it
does. And you'll have to lobby against a -1 of course.
I agree that new projects should be discussed before launching of on a sandbox commit. However, I do think that the notion of "project" should be qualified. For example, the merlin-jndi package reflects good structuring and separation of concerns within and across the Merlin system. It's all part of the Merlin "project" (from a functional perspective).
If the structural breakout is problematic it could be repackage but this would be nothing more that moving deck-chairs. The current Merlin suite presently includes:
merlin core merlin implementation merlin-spi Merlin Service Provider Interface API merlin-jndi Merlin JNDI Connector merlin-bootstrap Merlin CLI loader
Cheers, Steve.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]://www.osm.net
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
