First, I agree with Jeff that we should start with a simple thing and make it run, then we can make it bigger and bigger. Second, regarding the for the deployment thing, although we can consider it something separate than the implementation of clustering, I mean we can manage this by ourselves for testing only and after having a running clustering impl we can go and impl this feature, but I want to add two ideas about it just for the record.
1- Clustered/Distributed naming service, that is when I send a look-up request to a naming service, and this naming service does not find what I want, it can get benefit from the cluster infrastructure to locate other naming services either to redirect the client to it or to play like a delegate of the client and return back the looked-up object. This is the expensive solution IMO. 2- Cluster deployment manager, that is we have a cluster deployer, a deployer which can benefit from the clustering infrastructure to locate all servers in the cluster to deploy any EJB module being deployed on all of them. This is the less expensive solution IMO. But all this depends on providing the clustering infra structure into OEJB, which we have to make it pluggable as Jeff said, so we can make OpenEJB work with any clustering implementation. I think we can provide this the same way Sun specifies services for JEE and how to integrate them into a Server/Container like JTS/JTA and security services for JEE. So as Jeff said we have to start stating the SPI for both how to plugin the clustring infrastructure into OEJB and the server election policy into the clients/stubs, and the APIs provided for both the server side and client side to use this clustering infrastructure service. On 6/15/07, Jeff Genender <[EMAIL PROTECTED]> wrote:
Paulo Lopes wrote: > Another issue that hasn't been discussed is what happens when the > nodes are not synchronized? I deploy a EJB on node #1 but my initial > context sends me to node #2... if we are talking about clustering we > need also to consider a change on the deployer so it deploys any new > EJB on all the nodes of the cluster... Isn't this a facet of the clustering implementation?
-- Thanks - Mohammad Nour
