Author: vanto
Date: Fri Dec 28 11:49:36 2012
New Revision: 1426473
URL: http://svn.apache.org/viewvc?rev=1426473&view=rev
Log:
fix formatting
Modified:
ode/site/trunk/content/ws-bpel-20-specification-compliance.mdtext
Modified: ode/site/trunk/content/ws-bpel-20-specification-compliance.mdtext
URL:
http://svn.apache.org/viewvc/ode/site/trunk/content/ws-bpel-20-specification-compliance.mdtext?rev=1426473&r1=1426472&r2=1426473&view=diff
==============================================================================
--- ode/site/trunk/content/ws-bpel-20-specification-compliance.mdtext (original)
+++ ode/site/trunk/content/ws-bpel-20-specification-compliance.mdtext Fri Dec
28 11:49:36 2012
@@ -1,5 +1,5 @@
Title: WS-BPEL 2.0 Specification Compliance
-This page provides information on ODE's compliance to the final [WS-BPEL
2.0](ws-bpel-2.0.html) specification released by OASIS. ODE also implements [a
few extensions|BPEL Extensions] we deemed necessary.
+This page provides information on ODE's compliance to the final [WS-BPEL
2.0](ws-bpel-2.0.html) specification released by OASIS. ODE also implements [a
few extensions](bpel-extensions.html) we deemed necessary.
<a name="WS-BPEL2.0SpecificationCompliance-StaticAnalysis"></a>
## Static Analysis
@@ -22,8 +22,8 @@ In addition to regular variables that ar
## Activities
In this section the divergences from the specification for each standard BPEL
activity are described.
-<a name="WS-BPEL2.0SpecificationCompliance-`<[receive](receive.html)>`"></a>
-### `<`[`receive`](receive.html)`>`
+<a name="WS-BPEL2.0SpecificationCompliance-receive"></a>
+### <[receive](receive.html)>
There are several major issues with support for the `<receive>` activity.
ODE does not yet support the `<fromPart>` syntax. Therefore, the `variable`
attribute must be used. Furthermore, only message variables can be referenced
with the `variable` attribute, whereas the [specification](ws-bpel-2.0.html)
permits referencing of an element-typed variable if the WSDL for the request
message contains a single element-typed part.
@@ -39,23 +39,23 @@ ODE does not provide the ordering guaran
is illegal according to the BPEL specification, but allowed by ODE.
-The specification defines two standard faults ---
`bpel:[conflictingRequest](conflictingrequest.html)` and
`bpel:[conflictingReceive]` --- 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 `conflictingReceive` is thrown whenever either of the
conditions occurs. That is to say, in certain cases a `conflictingReceive`
indicates a `conflictingRequest`, and `conflictingRequest` is never thrown.
+The specification defines two standard faults ---
`bpel:[conflictingRequest](conflictingrequest.html)` and
`bpel:[conflictingReceive](conflictingreceive.html)` --- 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 `conflictingReceive` is thrown whenever either of the
conditions occurs. That is to say, in certain cases a `conflictingReceive`
indicates a `conflictingRequest`, and `conflictingRequest` is never thrown.
Finally, the `validate` attribute --- if present --- is ignored: ODE currently
provides no variable validation.
-<a name="WS-BPEL2.0SpecificationCompliance-`<[reply](reply.html)>`"></a>
-### `<[reply](reply.html)>`
+<a name="WS-BPEL2.0SpecificationCompliance-reply"></a>
+### <[reply](reply.html)>
The conformance issues with the `<reply>` activity mirror those of the
`<receive>` activity as described above: the `<toPart>` syntax is not
supported, and `variable` attributes must reference message-typed variables.
-<a name="WS-BPEL2.0SpecificationCompliance-`<[invoke](invoke.html)>`"></a>
-### `<[invoke](invoke.html)>`
+<a name="WS-BPEL2.0SpecificationCompliance-invoke"></a>
+### <[invoke](invoke.html)>
Again, as in the `<receive>>` and `<reply>` activities, the `<toPart>>` and
`<fromPart>>` syntax are not supported. Similarly, the `inputVariable` and
`outputVariable` attributes must reference message-typed variables. Here too,
the `validate` attribute is ignored.
-<a name="WS-BPEL2.0SpecificationCompliance-`<[assign](assign.html)>`"></a>
-### `<[assign](assign.html)>`
-The WS-BPEL 2.0 specification requires the `<[assign](assign.html)>` activity
to be atomic. Currently in ODE, each `<copy>` is atomic.
+<a name="WS-BPEL2.0SpecificationCompliance-assign"></a>
+### <[assign](assign.html)>
+The WS-BPEL 2.0 specification requires the <[assign](assign.html)> activity to
be atomic. Currently in ODE, each `<copy>` is atomic.
-The specification also provides for validating variables at the end of an
assignment using the `validate` attribute. ODE does not support this. This
means that the `bpel:[invalidVariables](invalidvariables.html)` fault is never
thrown by an `<[assign]>` activity.
+The specification also provides for validating variables at the end of an
assignment using the `validate` attribute. ODE does not support this. This
means that the `bpel:[invalidVariables](invalidvariables.html)` fault is never
thrown by an <[assign](assign.html)> activity.
Inline assignment as part of the variable declaration isn't currently
supported.
@@ -63,72 +63,72 @@ ODE currently uses the `expressionLangua
There are no other known divergences from the specification relating to the
`<assign>` activity that would prevent the execution of valid BPEL assignments.
ODE provides certain (non-standard) extensions to the `<assign>` activity that
do not conform to the specification's requirements for assignment extensions.
Consult the [reference page](assign.html) for the `<assign>` activity for
further details regarding non-standard extensions.
-<a name="WS-BPEL2.0SpecificationCompliance-`<[throw](throw.html)>`"></a>
-### `<[throw](throw.html)>`
+<a name="WS-BPEL2.0SpecificationCompliance-throw"></a>
+### <[throw](throw.html)>
The `<throw>` activity is fully compliant with the specification.
-<a name="WS-BPEL2.0SpecificationCompliance-`<[exit](exit.html)>`"></a>
-### `<[exit](exit.html)>`
+<a name="WS-BPEL2.0SpecificationCompliance-exit"></a>
+### <[exit](exit.html)>
The `<exit>` activity is fully compliant with the specification.
-<a name="WS-BPEL2.0SpecificationCompliance-`<[wait](wait.html)>`"></a>
-### `<[wait](wait.html)>`
+<a name="WS-BPEL2.0SpecificationCompliance-wait"></a>
+### <[wait](wait.html)>
The `<wait>` activity is fully compliant with the specification.
-<a name="WS-BPEL2.0SpecificationCompliance-`<[empty](empty.html)>`"></a>
-### `<[empty](empty.html)>`
+<a name="WS-BPEL2.0SpecificationCompliance-empty"></a>
+### <[empty](empty.html)>
The `<empty>` activity is fully compliant with the specification.
-<a name="WS-BPEL2.0SpecificationCompliance-`<[sequence](sequence.html)>`"></a>
-### `<[sequence](sequence.html)>`
+<a name="WS-BPEL2.0SpecificationCompliance-sequence"></a>
+### <[sequence](sequence.html)>
The `<sequence>` activity is fully compliant with the specification.
-<a name="WS-BPEL2.0SpecificationCompliance-`<[if](if.html)>`"></a>
-### `<[if](if.html)>`
+<a name="WS-BPEL2.0SpecificationCompliance-if"></a>
+### <[if](if.html)>
The `<if>` activity is fully compliant with the specification.
-<a name="WS-BPEL2.0SpecificationCompliance-`<[while](while.html)>`"></a>
-### `<[while](while.html)>`
+<a name="WS-BPEL2.0SpecificationCompliance-while"></a>
+### <[while](while.html)>
The `<while>` activity is fully compliant with the specification.
-<a
name="WS-BPEL2.0SpecificationCompliance-`<[repeatUntil](repeatuntil.html)>`"></a>
-### `<[repeatUntil](repeatuntil.html)>`
+<a name="WS-BPEL2.0SpecificationCompliance-repeatUntil"></a>
+### <[repeatUntil](repeatuntil.html)>
The `<repeatUntil>` activity is fully compliant with the specification.
-<a name="WS-BPEL2.0SpecificationCompliance-`<[forEach](foreach.html)>`"></a>
-### `<[forEach](foreach.html)>`
+<a name="WS-BPEL2.0SpecificationCompliance-forEach"></a>
+### <[forEach](foreach.html)>
The `<forEach>` activity is fully compliant with the specification. ODE
supports both sequential and parallel for-each semantics.
-<a name="WS-BPEL2.0SpecificationCompliance-`<[pick](pick.html)>`"></a>
-### `<[pick](pick.html)>`
-The `<[pick](pick.html)>` activity has the same issues as the `<[receive]>`
activity.
+<a name="WS-BPEL2.0SpecificationCompliance-pick"></a>
+### <[pick](pick.html)>
+The <[pick](pick.html)> activity has the same issues as the
<[receive](receive.html)> activity.
-<a name="WS-BPEL2.0SpecificationCompliance-`<[flow](flow.html)>`"></a>
-### `<[flow](flow.html)>`
+<a name="WS-BPEL2.0SpecificationCompliance-flow`"></a>
+### <[flow](flow.html)>
The `<flow>` activity is fully compliant with the specification.
-<a name="WS-BPEL2.0SpecificationCompliance-`<[scope](scope.html)>`"></a>
-### `<[scope](scope.html)>`
-Isolated scopes are implemented in ODE trunk (as of September 2007) and will
be released in ODE 1.2/2.0.
+<a name="WS-BPEL2.0SpecificationCompliance-scope"></a>
+### <[scope](scope.html)>
+Isolated scopes are implemented in ODE's experimental branch (as of September
2007) and will be released in ODE 2.x.
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 `isolated` and `exitOnStandardFault` attributes on `<scope>` elements did
not exist.
-<a
name="WS-BPEL2.0SpecificationCompliance-`<[compensate](compensate.html)>`"></a>
-### `<[compensate](compensate.html)>`
+<a name="WS-BPEL2.0SpecificationCompliance-compensate"></a>
+### <[compensate](compensate.html)>
The `<compensate>` activity is not compliant with the specification. In ODE,
this activity has the same effect and syntax as `<compensateScope>`. In
addition, the `scope` attribute may be used in place of the `target` attribute
with the same effect; and ODE expects one of these attributes must be
specified.
-<a
name="WS-BPEL2.0SpecificationCompliance-`<[compensateScope](compensatescope.html)>`"></a>
-### `<[compensateScope](compensatescope.html)>`
+<a name="WS-BPEL2.0SpecificationCompliance-compensateScope"></a>
+### <[compensateScope](compensatescope.html)>
The `<compensateScope>` activity is fully compliant with the specification.
-<a name="WS-BPEL2.0SpecificationCompliance-`<[rethrow](rethrow.html)>`"></a>
-### `<[rethrow](rethrow.html)>`
+<a name="WS-BPEL2.0SpecificationCompliance-rethrow"></a>
+### <[rethrow](rethrow.html)>
The `<rethrow>` activity is fully compliant with the specification.
-<a name="WS-BPEL2.0SpecificationCompliance-`<[validate](validate.html)>`"></a>
-### `<[validate](validate.html)>`
+<a name="WS-BPEL2.0SpecificationCompliance-validate"></a>
+### <[validate](validate.html)>
The `<validate>` activity is _not_ implemented by ODE. Processescontaining
such activities will cause a compilation failure.
-<a
name="WS-BPEL2.0SpecificationCompliance-`<[extensionActivity](extensionactivity.html)>`"></a>
-### `<[extensionActivity](extensionactivity.html)>`
+<a name="WS-BPEL2.0SpecificationCompliance-extensionActivity"></a>
+### <[extensionActivity](extensionactivity.html)>
Activity extension is not supported in ODE. There is an implementation in the
ODE experimental branch.
