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 --- .../sca-java-implementationbpel.html | 192 +++++++++++++++++++++ 1 file changed, 192 insertions(+) create mode 100644 site/trunk/site-publish/documentation-2x/sca-java-implementationbpel.html (limited to 'site/trunk/site-publish/documentation-2x/sca-java-implementationbpel.html') diff --git a/site/trunk/site-publish/documentation-2x/sca-java-implementationbpel.html b/site/trunk/site-publish/documentation-2x/sca-java-implementationbpel.html new file mode 100644 index 0000000000..1d824bb1af --- /dev/null +++ b/site/trunk/site-publish/documentation-2x/sca-java-implementationbpel.html @@ -0,0 +1,192 @@ + + + + + + + + + + + + + + + SCA Java implementation.bpel : Apache Tuscany + + + + + + + + + + + +
+ HomeApache Tuscany Docs 2.x > Index > SCA Java Extensions Guide > SCA Java implementation.bpel + +
+ + + + + + +
+
+ + + + + + + + +
+  Apache Tuscany Docs 2.x > Index > SCA Java Extensions Guide > SCA Java implementation.bpel + + Tuscany Home | User List | Dev List | Issue Tracker   +
+ + + + + + +
+
Table of Contents
+
+ + +
+
+ +
+ + +
+
+

Introduction

+ +

This is a initial WS-BPEL component implementation that allows SCA runtime to invoke WS-BPEL executable processes in a SCA composition.
+We are still working to finalize the Reference support, to allow your BPEL process to have partnerLinks pointing to SCA components.

+ +

As for creating a SCA component, below is an sample SCDL

+ +
+
+<composite xmlns="http://www.osoa.org/xmlns/sca/1.0"
+	targetNamespace="http://bpel"
+    xmlns:hns="http://tuscany.apache.org/implementation/bpel/example/helloworld"
+    name="bpel">
+    
+    <component name="BPELHelloWorldComponent">
+        <implementation.bpel process="hns:HelloWorld"/>
+    </component>
+
+</composite>
+
+
+ + +

WS-BPEL Engine

+ +

As for a WS-BPEL engine, we are using Apache ODE. In order to properly deploy a WS-BPEL process in ODE, a deployment descriptor like the one below should be suplied with your application :

+ +
+
+<deploy xmlns="http://www.apache.org/ode/schemas/dd/2007/03"
+	xmlns:tns="http://tuscany.apache.org/implementation/bpel/example/helloworld" 
+	xmlns:wns="http://tuscany.apache.org/implementation/bpel/example/helloworld.wsdl">
+
+
+	<process name="tns:HelloWorld">
+		<active>true</active>
+		<provide partnerLink="helloPartnerLink">
+			<service name="wns:HelloService" port="HelloPort"/>
+		</provide>
+	</process>
+</deploy>
+
+
+ +

For more information on these deployment descriptors, see documentation on Deploying a process in ODE

+ + +

References

+ +

SCA & BPEL white paper

+ +

SCA Client Implementation Model for BPEL v1.00

+
+ +
+
+
+ + + + + + + +
+ + + \ No newline at end of file -- cgit v1.2.3