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 22:27:28 UTC
svn commit: r844169 - in /websites/staging/ode/trunk/content: ./
ws-bpel-20-specification-compliance.html
Author: buildbot
Date: Fri Dec 28 21:27:28 2012
New Revision: 844169
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 21:27:28 2012
@@ -1 +1 @@
-1426638
+1426639
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 21:27:28 2012
@@ -115,7 +115,7 @@
<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-reply"></a></p>
-<h3 id="reply"><<a href="reply.html">reply</a>></h3>
+<h3 id="wzxhzdk15"><reply></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-invoke"></a></p>
<h3 id="invoke"><<a href="invoke.html">invoke</a>></h3>
@@ -128,56 +128,56 @@
<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-throw"></a></p>
-<h3 id="throw"><<a href="throw.html">throw</a>></h3>
+<h3 id="wzxhzdk22"><throw></h3>
<p>The <code><throw></code> activity is fully compliant with the specification.</p>
<p><a name="WS-BPEL2.0SpecificationCompliance-exit"></a></p>
-<h3 id="exit"><<a href="exit.html">exit</a>></h3>
+<h3 id="wzxhzdk25"><exit></h3>
<p>The <code><exit></code> activity is fully compliant with the specification.</p>
<p><a name="WS-BPEL2.0SpecificationCompliance-wait"></a></p>
-<h3 id="wait"><<a href="wait.html">wait</a>></h3>
+<h3 id="wzxhzdk28"><wait></h3>
<p>The <code><wait></code> activity is fully compliant with the specification.</p>
<p><a name="WS-BPEL2.0SpecificationCompliance-empty"></a></p>
-<h3 id="empty"><<a href="empty.html">empty</a>></h3>
+<h3 id="wzxhzdk31"><empty></h3>
<p>The <code><empty></code> activity is fully compliant with the specification.</p>
<p><a name="WS-BPEL2.0SpecificationCompliance-sequence"></a></p>
-<h3 id="sequence"><<a href="sequence.html">sequence</a>></h3>
+<h3 id="wzxhzdk34"><sequence></h3>
<p>The <code><sequence></code> activity is fully compliant with the specification.</p>
<p><a name="WS-BPEL2.0SpecificationCompliance-if"></a></p>
-<h3 id="if"><<a href="if.html">if</a>></h3>
+<h3 id="wzxhzdk37"><if></h3>
<p>The <code><if></code> activity is fully compliant with the specification.</p>
<p><a name="WS-BPEL2.0SpecificationCompliance-while"></a></p>
-<h3 id="while"><<a href="while.html">while</a>></h3>
+<h3 id="wzxhzdk40"><while></h3>
<p>The <code><while></code> activity is fully compliant with the specification.</p>
<p><a name="WS-BPEL2.0SpecificationCompliance-repeatUntil"></a></p>
-<h3 id="repeatuntil"><<a href="repeatuntil.html">repeatUntil</a>></h3>
+<h3 id="wzxhzdk43"><repeatUntil></h3>
<p>The <code><repeatUntil></code> activity is fully compliant with the specification.</p>
<p><a name="WS-BPEL2.0SpecificationCompliance-forEach"></a></p>
-<h3 id="foreach"><<a href="foreach.html">forEach</a>></h3>
+<h3 id="wzxhzdk46"><forEach></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-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>
+<h3 id="wzxhzdk51"><flow></h3>
<p>The <code><flow></code> activity is fully compliant with the specification.</p>
<p><a name="WS-BPEL2.0SpecificationCompliance-scope"></a></p>
-<h3 id="scope"><<a href="scope.html">scope</a>></h3>
+<h3 id="wzxhzdk54"><scope></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-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-compensateScope"></a></p>
-<h3 id="compensatescope"><<a href="compensatescope.html">compensateScope</a>></h3>
+<h3 id="wzxhzdk59"><compensateScope></h3>
<p>The <code><compensateScope></code> activity is fully compliant with the specification.</p>
<p><a name="WS-BPEL2.0SpecificationCompliance-rethrow"></a></p>
-<h3 id="rethrow"><<a href="rethrow.html">rethrow</a>></h3>
+<h3 id="wzxhzdk62"><rethrow></h3>
<p>The <code><rethrow></code> activity is fully compliant with the specification.</p>
<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-extensionActivity"></a></p>
-<h3 id="extensionactivity"><<a href="extensionactivity.html">extensionActivity</a>></h3>
+<h3 id="wzxhzdk67"><extensionActivity></h3>
<p>Activity extension is not supported in ODE. There is an implementation in the ODE experimental branch.</p>
</div>
</div>