Start of a binding that uses Hazelcast. The idea is that it would be used for the sca binding and use the Hazelcast based endpoint registry with Hazelcast handling all the remote communications. This avoids all the issues other bindings have with working out what the remote endpoint address is.

git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@924789 13f79535-47bb-0310-9956-ffa450edef68

1 files changed, 19 insertions, 0 deletions

diff --git a/sca-java-2.x/trunk/modules/binding-hazelcast-runtime/META-INF/MANIFEST.MF b/sca-java-2.x/trunk/modules/binding-hazelcast-runtime/META-INF/MANIFEST.MF
new file mode 100644
index 0000000000..5783411181
--- /dev/null
+++ b/sca-java-2.x/trunk/modules/binding-hazelcast-runtime/META-INF/MANIFEST.MF
@@ -0,0 +1,19 @@
+Manifest-Version: 1.0

+SCA-Version: 1.1

+Bundle-Name: Apache Tuscany SCA Binding Hazelcast Runtime

+Bundle-Vendor: The Apache Software Foundation

+Bundle-Version: 2.0.0

+Bundle-ManifestVersion: 2

+Bundle-License: http://www.apache.org/licenses/LICENSE-2.0.txt

+Bundle-Description: Apache Tuscany Hazelcast Binding

+Bundle-SymbolicName: org.apache.tuscany.sca.binding.hazelcast.runtime

+Bundle-DocURL: http://www.apache.org/

+Bundle-RequiredExecutionEnvironment: J2SE-1.5,JavaSE-1.6
+Import-Package: com.hazelcast.config,

+ com.hazelcast.core,

+ com.hazelcast.nio,

+ org.apache.tuscany.sca.assembly;version="2.0.0",

+ org.apache.tuscany.sca.core;version="2.0.0",

+ org.apache.tuscany.sca.runtime;version="2.0.0"

+Export-Package: org.apache.tuscany.sca.endpoint.hazelcast;version="2.0.0";

+ uses:="org.apache.tuscany.sca.runtime,org.apache.tuscany.sca.assembly,org.apache.tuscany.sca.core"