At some stage, OpenEJB2 had some clustering stuff through WADI:
* When an EJB client was interacting with a node, on the way-back of
invocations or JNDI lookups, it was provided with a list of nodes
hosting the EJB targeted by the invocations or lookups;
* EJB clients were able to fail-over to other nodes if the primary
server was down;
* WADI was able to move statefull session beans from server to server.
This support has been removed as WADI's API was too unstable (a lot
of refactoring happened over the last months) and the implementation
was "not yet ready" for integration. I believe both of these problems
are now addressed :)
Thanks,
Gianny
On 17/06/2007, at 5:33 PM, Mohammad Nour El-Din wrote:
Actually the WADI site says that OpenEJB support is underway, is this
related to what we discuss here ???
On 6/17/07, Mohammad Nour El-Din <[EMAIL PROTECTED]> wrote:
Good pint Gianny, actually u maid me think about a new idea, can
we extend
WADI - http://incubator.apache.org/wadi/index.html - so it can
play as our
clustering infrastructure ???. Jeff comments ???
On 6/16/07, Gianny Damour <[EMAIL PROTECTED]> wrote:
>
> On 15/06/2007, at 6:39 AM, Jeff Genender wrote:
>
> > Awesome! Your help would be very much appreciated.
> >
> > I am flushing out the API now and I can post a patch (or just
> > commit it)
> > and we can alter it as need be.
> >
> > Should we start by talking about the SPI/API and maybe just start
> > posting the interfaces?
> Hello,
>
> It would be great to start with such a SPI/API. Also, do you think
> that you can propose the same SPI/API for Geronimo? There is
already
> an API there, which is sufficient for the clustering of HTTP
> sessions; and I suspect it now needs to be improved to support the
> clustering of stateful session beans.
>
> Please, fell free to post JIRAs or something somewhere with the
> proposed SPI/API such that we can contribute!
>
> Thanks,
> Gianny
>
>
> >
> > Jeff
>
>
--
Thanks
- Mohammad Nour
--
Thanks
- Mohammad Nour
