Please realize that I am still climbing the EJB and JBoss learning curve
myself. As long as the clients (which would include some EJBs in this
discussion) are using a specific nameserver, what difference does it make
what JBoss does with its own? In other words, if all clients are looking at
(e.g.) 192.168.1.100, then the fact that JBoss is running one at
localhost:1099 is immaterial. Right?
----- Original Message -----
From: "James Cook" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, April 02, 2001 9:24 AM
Subject: Re: [JBoss-user] Multiple Servers - Bean Locating
> So you are recommending a single name server as the solution.
>
> If so, how do you tell the jBoss to *not* use it's nameserver, or do you
still
> let it use its own nameserver, but its just a facade to another? A pointer
to
> documentation will do as well.
>
> jim
>
>
> ----- Original Message -----
> From: "Guy Rouillier" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, April 01, 2001 11:00 PM
> Subject: Re: [JBoss-user] Multiple Servers - Bean Locating
>
>
> > An EJB trying to locate another EJB is just like any other client trying
to
> > locate an EJB. Use JNDI to look up the EJBs from a known location. In
a
> > production environment, this will probably be something like LDAP.
> >
> > ----- Original Message -----
> > From: "James Cook" <[EMAIL PROTECTED]>
> > To: "Jboss-User@Lists. Sourceforge. Net"
<[EMAIL PROTECTED]>
> > Sent: Sunday, April 01, 2001 1:08 AM
> > Subject: [JBoss-user] Multiple Servers - Bean Locating
> >
> >
> > > I'm trying to get a handle on how jBoss can be used to distribute an
> > > application. In development (and sometimes in production) all of the
beans
> > > that an application needs may not be located in the same container.
How
> > can
> > > a bean in one container talk to a bean in another container? I could
not
> > > find anything in the docs that explained this very well.
> > >
> > > Solution #1
> > > ===========
> > > I saw a newsgroup message where the author was relating a technique
for
> > > using the <ejb-link> tag in the jboss.xml file to include a url like:
> > > jndi://host:port/path/to/object, or something like that. If this
works,
> > > good, but it significantly impacts the deployment process if every
bean is
> > > hardcoded, although it is via deployment descriptors.
> > >
> > > Solution #2
> > > ===========
> > > I was thinking I could run only one of the jBoss servers with a naming
> > > service. The other servers would be configured to use the name service
of
> > > the first container. Whenever a client or another EJB needed a
reference
> > to
> > > a bean they would *all* look it up in the same location.
> > >
> > > Solution #3
> > > ===========
> > > I read in the docs about the possibility of federating namespaces.
Each
> > > server's name service could be federated into one name service that
> > clients
> > > and jBoss containers would use for lookup.
> > >
> > > So what is possible to achieve this today? Are some other more robust
> > > solutions waiting for the clustering architecture to work its way out?
> > Where
> > > are the ideas for future direction discussed or documented?
> > >
> > > thanks,
> > > jim
> > >
> > >
> > > _______________________________________________
> > > JBoss-user mailing list
> > > [EMAIL PROTECTED]
> > > http://lists.sourceforge.net/lists/listinfo/jboss-user
> > >
> >
> >
> > _______________________________________________
> > JBoss-user mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/jboss-user
> >
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
