You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@ode.apache.org by va...@apache.org on 2012/12/28 12:40:43 UTC

svn commit: r1426470 - /ode/site/trunk/content/ws-bpel-20-specification-compliance.mdtext

Author: vanto
Date: Fri Dec 28 11:40:43 2012
New Revision: 1426470

URL: http://svn.apache.org/viewvc?rev=1426470&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=1426470&r1=1426469&r2=1426470&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:40:43 2012
@@ -23,7 +23,7 @@ In addition to regular variables that ar
 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)>
+### `<`[`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.