Laurent wrote:


I'm playing with the Merlin JNDI stuff, but the documentation
still looks somehow obscure to me. What are the expected JNDI
environment parameters (standard ones such as
Context.INITIAL_CONTEXT_FACTORY and Context.OBJECT_FACTORIES
(which I assume should include Merlin ServiceFactory, that is
org.apache.avalon.merlin.jndi.ServiceFactory), but also custom
ones) ? A look at the server.xml file mentioned in the
documentation would probably help !

Here is a snipet of a <DefaultContext> declaration included in a <host> element in a server.xml file I have locally.

<DefaultContext debug="0">

          <Resource name="merlin/ServiceFactory" auth="Container"
type="org.apache.avalon.merlin.jndi.Service"/>
          <ResourceParams name="merlin/ServiceFactory">
            <parameter>
              <name>factory</name>
              <value>org.apache.avalon.merlin.jndi.ServiceFactory</value>
            </parameter>
            <parameter>
              <name>kernel</name>
              <value>F:/system/merlin/config/kernel.xml</value>
            </parameter>
            <parameter>
              <name>system</name>
              <value>F:/system/merlin</value>
            </parameter>
            <parameter>
              <name>home</name>
              <value>F:/system/merlin/working</value>
            </parameter>
            <parameter>
              <name>block</name>
<value>file:/F:/somewhere/demo/block.xml</value>
            </parameter>
            <parameter>
              <name>debug</name>
              <value>DEBUG</value>
            </parameter>
          </ResourceParams>
        </DefaultContext>

Steve, you've been talking about a new JNDI provider wich would
provide service name resolution within a containment hierarchy (I
assume you're talking about having different namespaces relating to
different containers). What are the news ? I would love to give it a
try in a J2EE context (Web container and EJB container).


The first cut on the JNDI stuff in Merlin is basically a utility to access a Merlin kernel via JNDI. It is not what I want because it forces the implementation to code against the Kernel. What I wanted to implement was a JNDI provider that provided full naming and directory sorrort for service navigation across a containment model. What I have basically achieved is that I have a provider implementation that is serving as a personal training/learning/test-bed as I get to understand more of the JNDI semantics. I could commit it into sandbox if there are no objections.

Just at the moment I'm putting must of my thinking into the JMX side and how we achieve deep integration of JMX into the Assembly and Merlin system, and provide quality management tools on the desktop.

Cheers, Steve.

--

Stephen J. McConnell
mailto:[EMAIL PROTECTED]
http://www.osm.net

Sent via James running under Merlin as an NT service.
http://avalon.apache.org/sandbox/merlin








--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to