Thanks for all the responses. You all gave me the encouragement I needed to
pursue this through to the end (I really do need to get some sleep one of
these days.) Indeed, no source code changes are required, as I had hoped.
Here is the line that needs to change in jboss.xml in order to send the ejb
reference off to a different server:
<jndi-name>jnp://192.168.1.102:1099/guyr/DbSource</jndi-name>
In this example, guyr/DbSource is the name under which the EJB is deployed
on the other server, i.e., it's jndi-name on the other server.
Obviously, the correct way to do this is to just use a simple jndi-name
(without an explicit server), and then in the naming service, map that
jndi-name to the implementation. While in production we will probably be
using LDAP for this, I read the documentation on doing this in JBoss at
http://www.jboss.org/documentation/HTML/ch11s145.html. I'd like to ask for
clarification. From my reading of that chapter, it appears that the only
way to get a reference to an EJB on another server into JBoss's naming
service is to federate the entire namespace on that other server. Is that
understanding correct? Is it possible to add a single reference into
JBoss's naming service? In my example above, I'd like to add guyr/DbSource,
and tell it that this EJB can be found on server 192.168.1.102.
----- Original Message -----
From: "Scott M Stark" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, May 01, 2001 4:53 PM
Subject: Re: [JBoss-user] It never finds beans in another *.jar's
>
> That is not the correct understanding of the jndi-name element from the
jboss.xml
> descriptor. The docs show an example of an ejb-jar.xml of:
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
