Space: Apache Tuscany Docs 2.x
(http://cwiki.apache.org/confluence/display/TUSCANYxDOCx2x)
Page: SCA Java implementation.bpel
(http://cwiki.apache.org/confluence/display/TUSCANYxDOCx2x/SCA+Java+implementation.bpel)
Added by Luciano Resende:
---------------------------------------------------------------------
h3.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
{code}
<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>
{code}
h3.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 :
{code}
<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>
{code}
For more information on these deployment descriptors, see documentation on
[Deploying a process in ODE|http://ode.apache.org/creating-a-process.html]
h3.References
[SCA & BPEL white paper | http://osoa.org/display/Main/SCA+BPEL+White+Paper]
[SCA Client Implementation Model for BPEL v1.00 |
http://osoa.org/download/attachments/35/SCA_ClientAndImplementationModelforBPEL_V100.pdf?version=1]
Change your notification preferences:
http://cwiki.apache.org/confluence/users/viewnotifications.action
