You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ode.apache.org by bu...@apache.org on 2012/12/28 12:49:45 UTC
svn commit: r844096 - in /websites/staging/ode/trunk/content: ./
ws-bpel-20-specification-compliance.html
Author: buildbot
Date: Fri Dec 28 11:49:44 2012
New Revision: 844096
Log:
Staging update by buildbot for ode
Modified:
websites/staging/ode/trunk/content/ (props changed)
websites/staging/ode/trunk/content/ws-bpel-20-specification-compliance.html
Propchange: websites/staging/ode/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Dec 28 11:49:44 2012
@@ -1 +1 @@
-1426470
+1426473
Modified: websites/staging/ode/trunk/content/ws-bpel-20-specification-compliance.html
==============================================================================
--- websites/staging/ode/trunk/content/ws-bpel-20-specification-compliance.html (original)
+++ websites/staging/ode/trunk/content/ws-bpel-20-specification-compliance.html Fri Dec 28 11:49:44 2012
@@ -83,7 +83,7 @@
<div class="row">
<div class="span12">
- <p>This page provides information on ODE's compliance to the final <a href="ws-bpel-2.0.html">WS-BPEL 2.0</a> specification released by OASIS. ODE also implements [a few extensions|BPEL Extensions] we deemed necessary.</p>
+ <p>This page provides information on ODE's compliance to the final <a href="ws-bpel-2.0.html">WS-BPEL 2.0</a> specification released by OASIS. ODE also implements <a href="bpel-extensions.html">a few extensions</a> we deemed necessary.</p>
<p><a name="WS-BPEL2.0SpecificationCompliance-StaticAnalysis"></a></p>
<h2 id="static-analysis">Static Analysis</h2>
<p>In this section the divergenced from the specification relating to static analysis requirements are described.</p>
@@ -98,8 +98,8 @@
<p><a name="WS-BPEL2.0SpecificationCompliance-Activities"></a></p>
<h2 id="activities">Activities</h2>
<p>In this section the divergences from the specification for each standard BPEL activity are described.</p>
-<p><a name="WS-BPEL2.0SpecificationCompliance-<code><[receive](receive.html)></code>"></a></p>
-<h3 id="receive"><code><</code><a href="receive.html"><code>receive</code></a><code>></code></h3>
+<p><a name="WS-BPEL2.0SpecificationCompliance-receive"></a></p>
+<h3 id="receive"><<a href="receive.html">receive</a>></h3>
<p>There are several major issues with support for the <code><receive></code> activity.</p>
<p>ODE does not yet support the <code><fromPart></code> syntax. Therefore, the <code>variable</code> attribute must be used. Furthermore, only message variables can be referenced with the <code>variable</code> attribute, whereas the <a href="ws-bpel-2.0.html">specification</a> permits referencing of an element-typed variable if the WSDL for the request message contains a single element-typed part.</p>
<p>Multiple start activities as described in section 10.4, and 15.4 of the <a href="ws-bpel-2.0.html">specification</a>) are not officially supported. This precludes the use of <code>initiate="join"</code>.</p>
@@ -112,72 +112,72 @@
<p>is illegal according to the BPEL specification, but allowed by ODE.</p>
-<p>The specification defines two standard faults --- <code>bpel:[conflictingRequest](conflictingrequest.html)</code> and <code>bpel:[conflictingReceive]</code> --- to deal with two similar error conditions relating to multiple outstanding requests on a single partner-link/operation/messageExchange tuple. ODE does not distinguish between these two conditions and <code>conflictingReceive</code> is thrown whenever either of the conditions occurs. That is to say, in certain cases a <code>conflictingReceive</code> indicates a <code>conflictingRequest</code>, and <code>conflictingRequest</code> is never thrown.</p>
+<p>The specification defines two standard faults --- <code>bpel:[conflictingRequest](conflictingrequest.html)</code> and <code>bpel:[conflictingReceive](conflictingreceive.html)</code> --- to deal with two similar error conditions relating to multiple outstanding requests on a single partner-link/operation/messageExchange tuple. ODE does not distinguish between these two conditions and <code>conflictingReceive</code> is thrown whenever either of the conditions occurs. That is to say, in certain cases a <code>conflictingReceive</code> indicates a <code>conflictingRequest</code>, and <code>conflictingRequest</code> is never thrown.</p>
<p>Finally, the <code>validate</code> attribute --- if present --- is ignored: ODE currently provides no variable validation.</p>
-<p><a name="WS-BPEL2.0SpecificationCompliance-<code><[reply](reply.html)></code>"></a></p>
-<h3 id="replyreplyhtml"><code><[reply](reply.html)></code></h3>
+<p><a name="WS-BPEL2.0SpecificationCompliance-reply"></a></p>
+<h3 id="reply"><<a href="reply.html">reply</a>></h3>
<p>The conformance issues with the <code><reply></code> activity mirror those of the <code><receive></code> activity as described above: the <code><toPart></code> syntax is not supported, and <code>variable</code> attributes must reference message-typed variables.</p>
-<p><a name="WS-BPEL2.0SpecificationCompliance-<code><[invoke](invoke.html)></code>"></a></p>
-<h3 id="invokeinvokehtml"><code><[invoke](invoke.html)></code></h3>
+<p><a name="WS-BPEL2.0SpecificationCompliance-invoke"></a></p>
+<h3 id="invoke"><<a href="invoke.html">invoke</a>></h3>
<p>Again, as in the <code><receive>></code> and <code><reply></code> activities, the <code><toPart>></code> and <code><fromPart>></code> syntax are not supported. Similarly, the <code>inputVariable</code> and <code>outputVariable</code> attributes must reference message-typed variables. Here too, the <code>validate</code> attribute is ignored.</p>
-<p><a name="WS-BPEL2.0SpecificationCompliance-<code><[assign](assign.html)></code>"></a></p>
-<h3 id="assignassignhtml"><code><[assign](assign.html)></code></h3>
-<p>The WS-BPEL 2.0 specification requires the <code><[assign](assign.html)></code> activity to be atomic. Currently in ODE, each <code><copy></code> is atomic.</p>
-<p>The specification also provides for validating variables at the end of an assignment using the <code>validate</code> attribute. ODE does not support this. This means that the <code>bpel:[invalidVariables](invalidvariables.html)</code> fault is never thrown by an <code><[assign]></code> activity.</p>
+<p><a name="WS-BPEL2.0SpecificationCompliance-assign"></a></p>
+<h3 id="assign"><<a href="assign.html">assign</a>></h3>
+<p>The WS-BPEL 2.0 specification requires the <<a href="assign.html">assign</a>> activity to be atomic. Currently in ODE, each <code><copy></code> is atomic.</p>
+<p>The specification also provides for validating variables at the end of an assignment using the <code>validate</code> attribute. ODE does not support this. This means that the <code>bpel:[invalidVariables](invalidvariables.html)</code> fault is never thrown by an <<a href="assign.html">assign</a>> activity.</p>
<p>Inline assignment as part of the variable declaration isn't currently supported.</p>
<p>ODE currently uses the <code>expressionLanguage</code> attribute to determine the language used in assignments instead of using the <code>queryLanguage</code> attribute.</p>
<p>There are no other known divergences from the specification relating to the <code><assign></code> activity that would prevent the execution of valid BPEL assignments. ODE provides certain (non-standard) extensions to the <code><assign></code> activity that do not conform to the specification's requirements for assignment extensions. Consult the <a href="assign.html">reference page</a> for the <code><assign></code> activity for further details regarding non-standard extensions.</p>
-<p><a name="WS-BPEL2.0SpecificationCompliance-<code><[throw](throw.html)></code>"></a></p>
-<h3 id="throwthrowhtml"><code><[throw](throw.html)></code></h3>
+<p><a name="WS-BPEL2.0SpecificationCompliance-throw"></a></p>
+<h3 id="throw"><<a href="throw.html">throw</a>></h3>
<p>The <code><throw></code> activity is fully compliant with the specification.</p>
-<p><a name="WS-BPEL2.0SpecificationCompliance-<code><[exit](exit.html)></code>"></a></p>
-<h3 id="exitexithtml"><code><[exit](exit.html)></code></h3>
+<p><a name="WS-BPEL2.0SpecificationCompliance-exit"></a></p>
+<h3 id="exit"><<a href="exit.html">exit</a>></h3>
<p>The <code><exit></code> activity is fully compliant with the specification.</p>
-<p><a name="WS-BPEL2.0SpecificationCompliance-<code><[wait](wait.html)></code>"></a></p>
-<h3 id="waitwaithtml"><code><[wait](wait.html)></code></h3>
+<p><a name="WS-BPEL2.0SpecificationCompliance-wait"></a></p>
+<h3 id="wait"><<a href="wait.html">wait</a>></h3>
<p>The <code><wait></code> activity is fully compliant with the specification.</p>
-<p><a name="WS-BPEL2.0SpecificationCompliance-<code><[empty](empty.html)></code>"></a></p>
-<h3 id="emptyemptyhtml"><code><[empty](empty.html)></code></h3>
+<p><a name="WS-BPEL2.0SpecificationCompliance-empty"></a></p>
+<h3 id="empty"><<a href="empty.html">empty</a>></h3>
<p>The <code><empty></code> activity is fully compliant with the specification.</p>
-<p><a name="WS-BPEL2.0SpecificationCompliance-<code><[sequence](sequence.html)></code>"></a></p>
-<h3 id="sequencesequencehtml"><code><[sequence](sequence.html)></code></h3>
+<p><a name="WS-BPEL2.0SpecificationCompliance-sequence"></a></p>
+<h3 id="sequence"><<a href="sequence.html">sequence</a>></h3>
<p>The <code><sequence></code> activity is fully compliant with the specification.</p>
-<p><a name="WS-BPEL2.0SpecificationCompliance-<code><[if](if.html)></code>"></a></p>
-<h3 id="ififhtml"><code><[if](if.html)></code></h3>
+<p><a name="WS-BPEL2.0SpecificationCompliance-if"></a></p>
+<h3 id="if"><<a href="if.html">if</a>></h3>
<p>The <code><if></code> activity is fully compliant with the specification.</p>
-<p><a name="WS-BPEL2.0SpecificationCompliance-<code><[while](while.html)></code>"></a></p>
-<h3 id="whilewhilehtml"><code><[while](while.html)></code></h3>
+<p><a name="WS-BPEL2.0SpecificationCompliance-while"></a></p>
+<h3 id="while"><<a href="while.html">while</a>></h3>
<p>The <code><while></code> activity is fully compliant with the specification.</p>
-<p><a name="WS-BPEL2.0SpecificationCompliance-<code><[repeatUntil](repeatuntil.html)></code>"></a></p>
-<h3 id="repeatuntilrepeatuntilhtml"><code><[repeatUntil](repeatuntil.html)></code></h3>
+<p><a name="WS-BPEL2.0SpecificationCompliance-repeatUntil"></a></p>
+<h3 id="repeatuntil"><<a href="repeatuntil.html">repeatUntil</a>></h3>
<p>The <code><repeatUntil></code> activity is fully compliant with the specification.</p>
-<p><a name="WS-BPEL2.0SpecificationCompliance-<code><[forEach](foreach.html)></code>"></a></p>
-<h3 id="foreachforeachhtml"><code><[forEach](foreach.html)></code></h3>
+<p><a name="WS-BPEL2.0SpecificationCompliance-forEach"></a></p>
+<h3 id="foreach"><<a href="foreach.html">forEach</a>></h3>
<p>The <code><forEach></code> activity is fully compliant with the specification. ODE supports both sequential and parallel for-each semantics.</p>
-<p><a name="WS-BPEL2.0SpecificationCompliance-<code><[pick](pick.html)></code>"></a></p>
-<h3 id="pickpickhtml"><code><[pick](pick.html)></code></h3>
-<p>The <code><[pick](pick.html)></code> activity has the same issues as the <code><[receive]></code> activity.</p>
-<p><a name="WS-BPEL2.0SpecificationCompliance-<code><[flow](flow.html)></code>"></a></p>
-<h3 id="flowflowhtml"><code><[flow](flow.html)></code></h3>
+<p><a name="WS-BPEL2.0SpecificationCompliance-pick"></a></p>
+<h3 id="pick"><<a href="pick.html">pick</a>></h3>
+<p>The <<a href="pick.html">pick</a>> activity has the same issues as the <<a href="receive.html">receive</a>> activity.</p>
+<p><a name="WS-BPEL2.0SpecificationCompliance-flow`"></a></p>
+<h3 id="flow"><<a href="flow.html">flow</a>></h3>
<p>The <code><flow></code> activity is fully compliant with the specification.</p>
-<p><a name="WS-BPEL2.0SpecificationCompliance-<code><[scope](scope.html)></code>"></a></p>
-<h3 id="scopescopehtml"><code><[scope](scope.html)></code></h3>
-<p>Isolated scopes are implemented in ODE trunk (as of September 2007) and will be released in ODE 1.2/2.0.</p>
+<p><a name="WS-BPEL2.0SpecificationCompliance-scope"></a></p>
+<h3 id="scope"><<a href="scope.html">scope</a>></h3>
+<p>Isolated scopes are implemented in ODE's experimental branch (as of September 2007) and will be released in ODE 2.x.</p>
<p>ODE v1.0/1.1 do not support isolated scopes nor do they support "exit on standard fault" semantics. Hence, a BPEL 2.0 process will be interpreted as if any <code>isolated</code> and <code>exitOnStandardFault</code> attributes on <code><scope></code> elements did not exist.</p>
-<p><a name="WS-BPEL2.0SpecificationCompliance-<code><[compensate](compensate.html)></code>"></a></p>
-<h3 id="compensatecompensatehtml"><code><[compensate](compensate.html)></code></h3>
+<p><a name="WS-BPEL2.0SpecificationCompliance-compensate"></a></p>
+<h3 id="compensate"><<a href="compensate.html">compensate</a>></h3>
<p>The <code><compensate></code> activity is not compliant with the specification. In ODE, this activity has the same effect and syntax as <code><compensateScope></code>. In addition, the <code>scope</code> attribute may be used in place of the <code>target</code> attribute with the same effect; and ODE expects one of these attributes must be specified.</p>
-<p><a name="WS-BPEL2.0SpecificationCompliance-<code><[compensateScope](compensatescope.html)></code>"></a></p>
-<h3 id="compensatescopecompensatescopehtml"><code><[compensateScope](compensatescope.html)></code></h3>
+<p><a name="WS-BPEL2.0SpecificationCompliance-compensateScope"></a></p>
+<h3 id="compensatescope"><<a href="compensatescope.html">compensateScope</a>></h3>
<p>The <code><compensateScope></code> activity is fully compliant with the specification.</p>
-<p><a name="WS-BPEL2.0SpecificationCompliance-<code><[rethrow](rethrow.html)></code>"></a></p>
-<h3 id="rethrowrethrowhtml"><code><[rethrow](rethrow.html)></code></h3>
+<p><a name="WS-BPEL2.0SpecificationCompliance-rethrow"></a></p>
+<h3 id="rethrow"><<a href="rethrow.html">rethrow</a>></h3>
<p>The <code><rethrow></code> activity is fully compliant with the specification.</p>
-<p><a name="WS-BPEL2.0SpecificationCompliance-<code><[validate](validate.html)></code>"></a></p>
-<h3 id="validatevalidatehtml"><code><[validate](validate.html)></code></h3>
+<p><a name="WS-BPEL2.0SpecificationCompliance-validate"></a></p>
+<h3 id="validate"><<a href="validate.html">validate</a>></h3>
<p>The <code><validate></code> activity is <em>not</em> implemented by ODE. Processescontaining such activities will cause a compilation failure.</p>
-<p><a name="WS-BPEL2.0SpecificationCompliance-<code><[extensionActivity](extensionactivity.html)></code>"></a></p>
-<h3 id="extensionactivityextensionactivityhtml"><code><[extensionActivity](extensionactivity.html)></code></h3>
+<p><a name="WS-BPEL2.0SpecificationCompliance-extensionActivity"></a></p>
+<h3 id="extensionactivity"><<a href="extensionactivity.html">extensionActivity</a>></h3>
<p>Activity extension is not supported in ODE. There is an implementation in the ODE experimental branch.</p>
</div>
</div>