Is the
requirement:
1. Be
able to use JNDI to find a Hivemind service in a single JVM?
or
2. Be
able to find the same reference to a Hivemind service across multiple
JVMs?
I
agree with Howard's take on (2). (1) is a bit more interesting. It is possible
to define a custom JNDI protocol that could facade the most frequently
occuring Hivemind service lookup,
RegistryBuilder.constructDefaultRegistry().
By
using a custom protocol you don't need to be serializable.
I'd be
happy to contribute an implementation to (1).
Cheers.
Naresh Sikha
-----Original Message-----
From: Howard M. Lewis Ship [mailto:[EMAIL PROTECTED]
Sent: Monday, May 24, 2004 11:37 AM
To: [email protected]
Subject: RE: Registry
From: Howard M. Lewis Ship [mailto:[EMAIL PROTECTED]
Sent: Monday, May 24, 2004 11:37 AM
To: [email protected]
Subject: RE: Registry
Binding it into JNDI seems to go counter to the expressly single JVM
nature of HiveMind. For sharing within an EAR, it works fine as a servlet
context attribute. Sharing between servers in a cluster is the wrong
approach ... instead, each server should have its own parallel Registry
instance.
What
with all the dynamic class creation and so forth, the Registry and the services,
proxies, interceptors and so forth are bad candidate for serialization. It takes
only a fraction of a second to construct the Registry. If you need to
communicate between servers, use JMS.
--
Howard M. Lewis Ship
Independent J2EE / Open-Source
Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
http://howardlewisship.com
-----Original Message-----Howard,
From: Pablo Lalloni [mailto:[EMAIL PROTECTED]
Sent: Monday, May 24, 2004 11:12 AM
To: [email protected]
Subject: Registry
We're trying to bind a Registry on JNDI but as it's not Serializable we can't...
Any chances of make Registry extend Serializable?
Is this possible?
Or there's any reason for it to not be?
Cheers,
Pablo
