Jim,
James Cook wrote:
>
> Thanks. I verified that a bean deployed on server1 can register itself in
> server2's namespace. However, if I deploy the same bean on server2, with the
> same namespace, the namespace can handle only one instance bound to the same
> name. The last bean bound, wins. This will solve some of my testing situations,
> so I thank you.
That's right, only one bean can be deployed.
But I didn't promised any loadbalancing.
We are using that to get an access to some NT-specific services.
And EJBs from the second server are just convenient wrappers.
> Moving forward, however, I would hope that I can deploy beans to two different
> containers, but have them located via a smarter naming service. When a client
> requests the bean, it will get the bean bound in server1. The next client would
> get the bean (bound under the same name) from server2. This would support a
> rudimentary form of load-balancing. If server1 crashes, the client's EJB
> reference will re-lookup the bean and be handed a remote reference to server2's
> bean. This would support failover.
I've been planing to extend the current Rickard's jnp name server for
similar
purposes, but didn't even started. Still a lot of stuff to do before.
--
__________________________________________________
Alexander Kogan PTC www.ptc.com
[EMAIL PROTECTED] 140 Kendrick St. Needham MA 02494
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
