From 200a40b332420f94992eb39a6d0ea1cf1490ffc4 Mon Sep 17 00:00:00 2001 From: coreyg Date: Fri, 21 Nov 2014 09:30:19 +0000 Subject: Adding tuscany's website to their svn repo for svnpubsub git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1640879 13f79535-47bb-0310-9956-ffa450edef68 --- .../site-publish/sca-java-binding-endpoints.html | 199 +++++++++++++++++++++ 1 file changed, 199 insertions(+) create mode 100644 site/trunk/site-publish/sca-java-binding-endpoints.html (limited to 'site/trunk/site-publish/sca-java-binding-endpoints.html') diff --git a/site/trunk/site-publish/sca-java-binding-endpoints.html b/site/trunk/site-publish/sca-java-binding-endpoints.html new file mode 100644 index 0000000000..ca3d2ef213 --- /dev/null +++ b/site/trunk/site-publish/sca-java-binding-endpoints.html @@ -0,0 +1,199 @@ + + + + + + + + + + + + + + + Apache Tuscany : SCA Java binding endpoints + + + + + + + + + + + + + + + +
+ + + + +   + +
+ + +
+
+ + + + + + + + + +
+  Apache Tuscany > Home > SCA Overview > SCA Java > Java SCA Documentation Menu > SCA Java binding endpoints + + User List | Dev List | Issue Tracker   +
+ + + + + + + +
+ + +
+ +
+
+ + +
+ + + + + + + + + + + +
Resources
+
+ +

SCA binding endpoints

+ +

The value of the endpoint URI used by an SCA service or reference binding is defined in the varrious SCA Specifications. The Assembly specification, page 53, section 1.7.2 "Form of the URI of a Deployed Binding" defines the overall rules, and specific binding specifications may modify or add addtional rules, for example, the Web service binding specifiction on page 3, section 2.1.1 "Endpoint URI resolution" adds further web service related endpoint rules.

+ +

The Tuscany runtime and binding implementations aim to all work consistently so that once you understand the basic endpoint URI rules and conventions it should be easy to determine an actual endpoint from reading the composite SCDL.

+ +

Some examples

+ +

The following composite fragment would result in the web service address of http://localhost:8080/MyService

+
+
+<composite xmlns="http://www.osoa.org/xmlns/sca/1.0"
+           name="MyComposite">
+
+    <service name="MyService" promote="SomeComponent">
+       <binding.ws/>
+    </service>
+
+    . . .
+
+</composite>
+
+
+ +

The following composite fragment would result in the web service address of http://localhost:8080/MyComponent/MyService

+
+
+<composite xmlns="http://www.osoa.org/xmlns/sca/1.0"
+           name="MyComposite">
+
+    <component name="MyComponent">
+        <service name="MyService">
+           <binding.ws/>
+        </service>
+        . . .
+    </component>
+
+</composite>
+
+
+ + +
+
+
+
+ + +
+ + + + + + website stats + + + + + + -- cgit v1.2.3