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 2013/07/09 10:42:53 UTC

svn commit: r1501134 - /ode/site/trunk/content/assign.mdtext

Author: vanto
Date: Tue Jul  9 08:42:52 2013
New Revision: 1501134

URL: http://svn.apache.org/r1501134
Log:
formatting

Modified:
    ode/site/trunk/content/assign.mdtext

Modified: ode/site/trunk/content/assign.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/assign.mdtext?rev=1501134&r1=1501133&r2=1501134&view=diff
==============================================================================
--- ode/site/trunk/content/assign.mdtext (original)
+++ ode/site/trunk/content/assign.mdtext Tue Jul  9 08:42:52 2013
@@ -1,68 +1,67 @@
 Title: assign
 <a name="assign-Name"></a>
-### Name
-`<assign>` --- {excerpt}update the values of variables with new data{excerpt}
+## Name
+`<assign>` --- update the values of variables with new data
  
 <a name="assign-Synopsis"></a>
-### Synopsis
-{code:xml title="Usage"}
-<assign validate="yes|no"? standard-attributes>
-   standard-elements
-   (
-   <copy keepSrcElementName="yes|no"? ignoreMissingFromData="yes|no"?>
-      from-spec
-      to-spec
-   </copy>
-   |
-   <extensionAssignOperation>
-      assign-element-of-other-namespace
-   </extensionAssignOperation>
-   )+
-</assign>
+## Synopsis
+<div class="caption">Usage</div>
+    <assign validate="yes|no"? standard-attributes>
+       standard-elements
+       (
+       <copy keepSrcElementName="yes|no"? ignoreMissingFromData="yes|no"?>
+          from-spec
+          to-spec
+       </copy>
+       |
+       <extensionAssignOperation>
+          assign-element-of-other-namespace
+       </extensionAssignOperation>
+       )+
+    </assign>
 
     
     *throws* `[bpel:invalidVariables](#invalidVariables)`, `[bpel:selectionFailure](#selectionFailure)`, `[bpel:subLanguageExecutionFault](#subLanguageExecutionFault)`, `[bpel:uninitializedVariable](#uninitializedVariable)`, `[bpel:mismatchedAssignmentFailure](#mismatchedAssignmentFailure)`, `[bpel:uninitializedPartnerRole](#uninitializedPartnerRole)`
     
     
     
-    h3. Description
-    The `<assign>` activity can be used to copy data from one variable to another, as well as to construct and insert new data using expressions. The `<assign>` activity can also be used to copy endpoint references to and from partnerLinks. 
-    
-    Each `<assign>` is made up of any number of `<copy>` entries which are each made up of a "to-spec" (lvalue), and a from-spec (rvalue). 
-    
-    - `ignoreMissingFromData` - (optional) Should the `[bpel:selectionFailure](#selectionFailure)` standard fault be suppressed? 
-    ** `yes` - suppress standard faults
-    ** `no` - (default) do not suppress standard faults
-    
-    {note}
+## Description
+The `<assign>` activity can be used to copy data from one variable to another, as well as to construct and insert new data using expressions. The `<assign>` activity can also be used to copy endpoint references to and from partnerLinks. 
+
+Each `<assign>` is made up of any number of `<copy>` entries which are each made up of a "to-spec" (lvalue), and a from-spec (rvalue). 
+
+ - `ignoreMissingFromData` - (optional) Should the `[bpel:selectionFailure](#selectionFailure)` standard fault be suppressed? 
+    - `yes` - suppress standard faults
+    - `no` - (default) do not suppress standard faults
+
+<div class="alert alert-info">
     The `ignoreMissingFromData` element has been implemented in ODE 1.3+ (i.e., it is coming soon).  See [ODE-141](http://issues.apache.org/jira/browse/ODE-141) for issue tracking.
-    {note}
-    
-    - `validate` - (optional) validate modified variables?
-    ** `yes` - the `<assign>` activity validates all the variables being modified by the activity. If the validation fails the `[bpel:invalidVariables#invalidVariables]` fault is thrown.
-    ** `no` - (default) do not validate the modified variables
-    {note}
+</div>
+
+ - `validate` - (optional) validate modified variables?
+    - `yes` - the `<assign>` activity validates all the variables being modified by the activity. If the validation fails the `[bpel:invalidVariables#invalidVariables]` fault is thrown.
+    - `no` - (default) do not validate the modified variables
+
+<div class="alert alert-info">
     ODE currently disregards the value of this attribute --- validation is never performed.
-    {note}
-    
-    - `<copy>` - defines a lvalue, rvalue pair.
-    -- `keepSrcElementName` - (optional) should the element name of the destination (as selected by the to-spec) be replaced by the elementname of the source (as selected by the from-spec)?
-    *** `yes` - element names are replaced
-    *** `no` - (default) element names are not replaced
-    -- `<from>` - specifies the rvalue (see [here](#variants))
-    -- `<to>` - specifies the lvalue (see [here](#variants))
-    
+</div>
+
+ - `<copy>` - defines a lvalue, rvalue pair.
+    - `keepSrcElementName` - (optional) should the element name of the destination (as selected by the to-spec) be replaced by the elementname of the source (as selected by the from-spec)?
+    - `yes` - element names are replaced
+    - `no` - (default) element names are not replaced
+    - `<from>` - specifies the rvalue (see [here](#variants))
+    - `<to>` - specifies the lvalue (see [here](#variants))
     - `<extensionAssignOperation>` - a container for assignment extensions. If the element contained within the extensionAssignOperation elements not recognized by ODE and is not subject to a mustUnderstand="yes" requirement from an extension declaration then the element will be ignored.
-    {note}
+
+<div class="alert alert-info">
     Since version 2.0 ODE fully supports `extensionAssingOperation` functionality.
-    {note}
-    
-    {anchor:variants}
-    h3. From/To-Spec Variants
-    
-    The <assign> activity copies a type-compatible value from the source ("from-spec") to the destination ("to-spec"), using the <copy> element. The from-spec must be one of the following variants:
-    
-    {code:xml}
+</div>
+
+### From/To-Spec Variants
+
+The <assign> activity copies a type-compatible value from the source ("from-spec") to the destination ("to-spec"), using the <copy> element. The from-spec must be one of the following variants:
+
     <from variable="BPELVariableName" part="NCName"?>
        <query queryLanguage="anyURI"?>?
           queryContent
@@ -87,7 +86,6 @@ Title: assign
 
     <from variable="BPELVariableName" extension="QName" />   <!-- non-standard extension -->
 
-
 <div class="alert alert-note">
     The `<from extension="QName" />` from-spec variant is not part of the WS-BPEL 2.0 specification. It is a non-standard ODE extension. 
 </div>
@@ -203,8 +201,8 @@ The empty variant exist for extensibilit
     <from|to/>
 
 
-<a name="assign-VariableExtensionVariant({color:red}non-standardextension{color})"></a>
-#### Variable Extension Variant ({color:red}non-standard extension{color})
+<a name="assign-VariableExtensionVariant(non-standardextension)"></a>
+#### Variable Extension Variant (non-standard extension)
 The variable extension variants are non-standard extensions implemented by ODE to allow manipulation of protocol-specific properties from within a BPEL process.
 
     <from variable="BPELVariableName" extension="QName" />