Author: vanto
Date: Fri Dec 28 11:35:38 2012
New Revision: 1426465
URL: http://svn.apache.org/viewvc?rev=1426465&view=rev
Log:
formatting test.
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=1426465&r1=1426464&r2=1426465&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:35:38 2012
@@ -1,9 +1,9 @@
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.
-
+
<a name="WS-BPEL2.0SpecificationCompliance-StaticAnalysis"></a>
## Static Analysis
-In this section the divergenced from the specification relating to static
analysis requirements are described.
+In this section the divergenced from the specification relating to static
analysis requirements are described.
<a name="WS-BPEL2.0SpecificationCompliance-Variables"></a>
## Variables
@@ -20,40 +20,40 @@ In addition to regular variables that ar
<a name="WS-BPEL2.0SpecificationCompliance-Activities"></a>
## Activities
-In this section the divergences from the specification for each standard BPEL
activity are described.
+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)>`
+### <pre><[receive](receive.html)></pre>
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.
+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.
-Multiple start activities as described in section 10.4, and 15.4 of the
[specification](ws-bpel-2.0.html)) are not officially supported. This precludes
the use of `initiate="join"`.
+Multiple start activities as described in section 10.4, and 15.4 of the
[specification](ws-bpel-2.0.html)) are not officially supported. This precludes
the use of `initiate="join"`.
-ODE does not provide the ordering guarantees described in section 10.4 of the
[specification](ws-bpel-2.0.html). Also, it does not enforce the ordering
requirements described in the same section. Hence, the BPEL code
+ODE does not provide the ordering guarantees described in section 10.4 of the
[specification](ws-bpel-2.0.html). Also, it does not enforce the ordering
requirements described in the same section. Hence, the BPEL code
- <flow>
- <receive ... createInstance="yes" />
- <assign ... />
+ <flow>
+ <receive ... createInstance="yes" />
+ <assign ... />
</flow>
-is illegal according to the BPEL specification, but allowed by ODE.
+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]` --- 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)>`
-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.
+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)>`
-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.
+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.
+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.
@@ -84,11 +84,11 @@ The `<empty>` activity is fully complian
The `<sequence>` activity is fully compliant with the specification.
<a name="WS-BPEL2.0SpecificationCompliance-`<[if](if.html)>`"></a>
-### `<[if](if.html)>`
+### `<[if](if.html)>`
The `<if>` activity is fully compliant with the specification.
<a name="WS-BPEL2.0SpecificationCompliance-`<[while](while.html)>`"></a>
-### `<[while](while.html)>`
+### `<[while](while.html)>`
The `<while>` activity is fully compliant with the specification.
<a
name="WS-BPEL2.0SpecificationCompliance-`<[repeatUntil](repeatuntil.html)>`"></a>
@@ -109,17 +109,17 @@ The `<flow>` activity is fully compliant
<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.
+Isolated scopes are implemented in ODE trunk (as of September 2007) and will
be released in ODE 1.2/2.0.
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)>`
-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.
+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)>`
-The `<compensateScope>` activity is fully compliant with the specification.
+The `<compensateScope>` activity is fully compliant with the specification.
<a name="WS-BPEL2.0SpecificationCompliance-`<[rethrow](rethrow.html)>`"></a>
### `<[rethrow](rethrow.html)>`
