how to use petals JNDI server

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

how to use petals JNDI server

rnaudin-3
In the Platform release, I need to use a JNDI server to store some information and I would like to use Petals' internal JNDI server as a service provider. Can I do that?

>From the topology.xml file, I see the NamingContextFactory class is defined but is commented out:

org.ow2.petals.communication.jndi.client.naming.NamingContextFactory

Is this the correct class?

I think I also need to configure the host and port. What's the default port number?

Anything else I need to configure such as the username/password?

Thanks.




-------------------- m2f --------------------

Read this forum topic online here:
http://petals.ebmwebsourcing.com/forum/viewtopic.php?p=379#379

-------------------- m2f --------------------

_______________________________________________
Users mailing list
[hidden email]
http://forum-list.petalslink.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: how to use petals JNDI server

rnaudin-3
Hi,

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? Shocked

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.




-------------------- m2f --------------------

Read this forum topic online here:
http://petals.ebmwebsourcing.com/forum/viewtopic.php?p=382#382

-------------------- m2f --------------------

_______________________________________________
Users mailing list
[hidden email]
http://forum-list.petalslink.org/cgi-bin/mailman/listinfo/users