summaryrefslogtreecommitdiffstats
path: root/sca-java-2.x/trunk/modules/endpoint-hazelcast (unfollow)
Commit message (Collapse)AuthorFilesLines
2010-02-09Start to clean up the node-api (remove Node.destroy())rfeng1-3/+3
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@908233 13f79535-47bb-0310-9956-ffa450edef68
2010-02-04Set default map config to use near cache to improve local endpoint read ↵antelder1-1/+5
performance git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@906581 13f79535-47bb-0310-9956-ffa450edef68
2010-01-29Update tribes registry to also support the tuscany registry uri formatantelder3-276/+3
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@904504 13f79535-47bb-0310-9956-ffa450edef68
2010-01-29Refactor the DomainRegistryFactory to be extensions of ↵rfeng3-111/+57
DomainRegistryFactoryExtensionPoint git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@904367 13f79535-47bb-0310-9956-ffa450edef68
2010-01-28Change the tuscanyClient scheme to pbe all lower case so it works with the ↵antelder1-4/+4
toLowerCase in the DefaultEndpointRegistryFactory, and move all the remote code in the scaclient to happen at invocation time. This now works for multiple local and remote nodes in one or separate JVMs git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@904206 13f79535-47bb-0310-9956-ffa450edef68
2010-01-28Update to allow the client to share this as a subclassantelder2-3/+7
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@904113 13f79535-47bb-0310-9956-ffa450edef68
2010-01-20Start of making the Tuscany sca client impl work for both local or remote ↵antelder1-18/+17
nodes and to be generic for any binding. Work in progress, only local invocations work presently git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@901270 13f79535-47bb-0310-9956-ffa450edef68
2010-01-19Expose system definitions from the deployerrfeng2-51/+265
Add the removal of entries when the member leaves the group Add listeners to the hazelcastInstance git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@900661 13f79535-47bb-0310-9956-ffa450edef68
2010-01-08Change the Hazelcast registry to support both distributed an in-VM only ↵antelder2-6/+16
operation git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@897140 13f79535-47bb-0310-9956-ffa450edef68
2010-01-06Refine MFrfeng1-2/+2
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@896656 13f79535-47bb-0310-9956-ffa450edef68
2010-01-06Updates to the Hazelcast regsitry manifestantelder1-16/+7
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@896648 13f79535-47bb-0310-9956-ffa450edef68
2010-01-05More changes to get the Hazelcast endpoint registry workingantelder7-578/+560
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@896269 13f79535-47bb-0310-9956-ffa450edef68
2010-01-05Start a endpoint registry based on Hazelcast. Hazelcast seems to do just ↵antelder6-0/+826
about everything we need and seems quite easy to use compared to other options. It supports multicast and explicit ip addresses, with ip addresses you only need to specifiy the address of one node and then all other nodes get notified about the new node. Hazelcast has various encryption options to secure the domain, and it has a way to have endpoints removed when a node disapears (though that requires a bit of code on our part to get to work). One limitation is currently it doesnt support multiple nodes using multicast, but they've said they can fix that. git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@896038 13f79535-47bb-0310-9956-ffa450edef68