Hi
I do not think that to use for each App server its own JNDI server
is a good idea because this would corrupt the idea of a naming and
directory service.
Wouldn't it be better to use a different path at each server (like a
domain name) instead?
Have fun - Mad Andy
----- Original Message -----
From: "Rickard �berg" <[EMAIL PROTECTED]>
To: "jBoss" <[EMAIL PROTECTED]>
Sent: Thursday, November 16, 2000 11:24 PM
Subject: Re: [jBoss-User] Multiple EJB servers
Hi!
> If so how do I configure this? On machines A and B I tried setting the
> provider in jndi.properties to machine C but then at startup I get:
>
> [JMX RMI Adaptor] javax.naming.NameAlreadyBoundException
Yeah, since this service (and many others) bind themselves into JNDI you
will have conflicts if you run one JNDI with several servers.
A better way to do it is to let each server have its own JNDI, and use
ejb-references in your beans to locate them. Then use jboss.xml to map
an ejb-reference to a complete JNDI name, e.g. let
"java:comp/env/ejb/MyEjb" map to "jnp://somehost/myapp/MyEjb". This way
you will have to configure the deployment descriptors for each bean, but
the bean source can use the hardcoded "java:" names.
regards,
Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
