apache-tuscany - apache tuscany

	Commit message (Collapse)	Author	Files	Lines
2010-10-25	Switch to use domain-hazelcast and remove old hazelcast mpodules	antelder	2	-305/+0
	git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1026995 13f79535-47bb-0310-9956-ffa450edef68
2010-06-05	Setting svn:eol-style for java and xml files	rfeng	1	-142/+142
	git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@951651 13f79535-47bb-0310-9956-ffa450edef68
2010-06-03	Update to corectly use loop back address in tests	antelder	1	-1/+7
	git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@950970 13f79535-47bb-0310-9956-ffa450edef68
2010-03-21	Update Hazelcast registry to check for duplicate endpoints	antelder	1	-0/+28
	git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@925745 13f79535-47bb-0310-9956-ffa450edef68
2010-03-09	Update Hazelcast endpoint registry to remove endpoints from a runtime that ↵	antelder	1	-80/+26
	no longer exists git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@921095 13f79535-47bb-0310-9956-ffa450edef68
2010-03-08	Update to Hazelcast 1.8.1	antelder	1	-1/+1
	git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@920181 13f79535-47bb-0310-9956-ffa450edef68
2010-01-29	Update tribes registry to also support the tuscany registry uri format	antelder	1	-106/+0
	git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@904504 13f79535-47bb-0310-9956-ffa450edef68
2010-01-19	Expose system definitions from the deployer	rfeng	1	-0/+183
	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-05	More changes to get the Hazelcast endpoint registry working	antelder	2	-0/+108
	git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@896269 13f79535-47bb-0310-9956-ffa450edef68
2010-01-05	Start a endpoint registry based on Hazelcast. Hazelcast seems to do just ↵	antelder	1	-0/+140
	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