Do you want to use the PEtALS internal JNDI server with an external client or do you want to use an external JNDI server with PEtALS?
In fact, it was possible to externalize the PEtALS internal JNDI server on a given PEtALS container with a given port, but this feature has been removed. It remains old factory name in the commented section of the topology.xml file.
It is possible to reactive it if necessary, but it would be available only on the trunk.
BUT, it is still possible to configure an external JNDI server for PEtALS, but this server won't be distributed as the PEtALS internal one.
For this, you must uncomment the parameters in the topology.xml file and set the correct JNDI factory, and the location of the JNDI server (a reachable host/port).
Note that this JNDI server is for PEtALS technical usage, and not made for being expose as a PETALS JBI service.
However, you can create your own JBI component to expose Naming service, and this component can use its dedicated NamingContext (componentContext.getNamingContext() )to store some Naming data.
This NamingContext is shared amongst all the components.