Author: buildbot
Date: Mon Dec 31 10:41:16 2012
New Revision: 844384
Log:
Staging update by buildbot for ode
Modified:
websites/staging/ode/trunk/content/ (props changed)
websites/staging/ode/trunk/content/extensions/extension-activities-extensible-assign-operations.html
websites/staging/ode/trunk/content/extensions/flexible-assigns.html
websites/staging/ode/trunk/content/extensions/headers-handling.html
websites/staging/ode/trunk/content/extensions/iterable-foreach.html
websites/staging/ode/trunk/content/extensions/restful-bpel-part-i.html
websites/staging/ode/trunk/content/extensions/restful-bpel-part-ii.html
Propchange: websites/staging/ode/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Dec 31 10:41:16 2012
@@ -1 +1 @@
-1427070
+1427075
Modified:
websites/staging/ode/trunk/content/extensions/extension-activities-extensible-assign-operations.html
==============================================================================
---
websites/staging/ode/trunk/content/extensions/extension-activities-extensible-assign-operations.html
(original)
+++
websites/staging/ode/trunk/content/extensions/extension-activities-extensible-assign-operations.html
Mon Dec 31 10:41:16 2012
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<html>
<head>
- <title>Apache ODE – Extension Activities & Extensible Assign
Operations
</title>
+ <title>Apache ODE – Extension Activities & Extensible Assign
Operations
</title>
<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
<meta property="og:image" content="http://ode.apache.org/img/ode-logo.png";
/>
@@ -72,7 +72,7 @@
<header class="jumbotron subhead" id="overview">
<div class="container">
- <h1>Extension Activities & Extensible Assign Operations
</h1>
+ <h1>Extension Activities & Extensible Assign Operations
</h1>
</div>
</header>
Modified: websites/staging/ode/trunk/content/extensions/flexible-assigns.html
==============================================================================
--- websites/staging/ode/trunk/content/extensions/flexible-assigns.html
(original)
+++ websites/staging/ode/trunk/content/extensions/flexible-assigns.html Mon Dec
31 10:41:16 2012
@@ -28,7 +28,7 @@
<li class="">
<a href="/getting-ode.html">Getting ODE</a>
</li>
- <li class=" dropdown">
+ <li class="active dropdown">
<a href="/user-guide.html" class="dropdown-toggle"
data-toggle="dropdown" data-target="#">Documentation<b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="/userguide/">User Guide</a></li>
@@ -92,28 +92,29 @@
1. Its steps have no following predicates, and
1. Its steps test the name of a node, without the use of wildcards. </p>
<p>Formally, the grammar of the to-spec, for which auto-complete is enabled,
may be defined in terms of these productions: </p>
-<div class="codehilite"><pre> <span class="n">RelativePathExpr</span> <span
class="o">::=</span> <span class="n">ForwardStep</span> <span
class="p">((</span><span class="s">"/"</span> <span
class="p">)</span> <span class="n">ForwardStep</span><span
class="p">)</span><span class="o">*</span>
- <span class="n">ForwardStep</span> <span class="o">::=</span> <span
class="p">(</span><span class="n">ForwardAxis</span> <span
class="n">QName</span><span class="p">)</span> <span class="o">|</span> <span
class="n">AbbrevForwardStep</span>
- <span class="n">AbbrevForwardStep</span> <span class="o">::=</span> <span
class="s">"@"</span><span class="o">?</span> <span
class="n">QName</span>
- <span class="n">ForwardAxis</span> <span class="o">::=</span> <span
class="p">(</span><span class="s">"child"</span> <span
class="s">"::"</span><span class="p">)</span> <span
class="o">|</span> <span class="p">(</span><span
class="s">"attribute"</span> <span
class="s">"::"</span><span class="p">)</span>
+<div class="codehilite"><pre>PathExpr ::= ("/" RelativePathExpr?) |
RelativePathExpr
+RelativePathExpr ::= ForwardStep (("/" ) ForwardStep)*
+ForwardStep ::= (ForwardAxis QName) | AbbrevForwardStep
+AbbrevForwardStep ::= "@"? QName
+ForwardAxis ::= ("child" "::") | ("attribute"
"::")
</pre></div>
<p>The example below illustrates the use of the insertMissingToData attribute.
Let's say that the variable "response" is uninitialized. In that case, the
first <copy> operation will fail, whereas the second one will succeed. </p>
-<div class="codehilite"><pre> <span class="nt"><copy></span>
- <span class="nt"><from></span><span class="p">$</span><span
class="nv">request</span><span class="p">.</span><span
class="nv">requestMessageData</span>/typeIndicators/types:indicatorTwo<span
class="nt"></from></span>
- <span class="nt"><to></span><span class="p">$</span><span
class="nv">response</span>/typeIndicators/types:indicatorTwo<span
class="nt"></to></span>
- <span class="nt"></copy></span>
+<div class="codehilite"><pre><span class="nt"><copy></span>
+ <span
class="nt"><from></span>$request.requestMessageData/typeIndicators/types:indicatorTwo<span
class="nt"></from></span>
+ <span
class="nt"><to></span>$response/typeIndicators/types:indicatorTwo<span
class="nt"></to></span>
+<span class="nt"></copy></span>
- <span class="nt"><copy</span> <span
class="na">insertMissingToData=</span><span
class="s">"yes"</span><span class="nt">></span>
- <span class="nt"><from></span><span class="p">$</span><span
class="nv">request</span><span class="p">.</span><span
class="nv">requestMessageData</span>/typeIndicators/types:indicatorTwo<span
class="nt"></from></span>
- <span class="nt"><to></span><span class="p">$</span><span
class="nv">response</span>/typeIndicators/child::types:indicatorTwo<span
class="nt"></to></span>
- <span class="nt"></copy></span>
+<span class="nt"><copy</span> <span
class="na">insertMissingToData=</span><span
class="s">"yes"</span><span class="nt">></span>
+ <span
class="nt"><from></span>$request.requestMessageData/typeIndicators/types:indicatorTwo<span
class="nt"></from></span>
+ <span
class="nt"><to></span>$response/typeIndicators/child::types:indicatorTwo<span
class="nt"></to></span>
+ <span class="nt"></copy></span>
</pre></div>
-<p><a
name="FlexibleAssigns-AddsupportfortheignoreMissingFromDataattributein<copy>"></a></p>
-<h2 id="add-support-for-the-ignoremissingfromdata-attribute-in-wzxhzdk11">Add
support for the ignoreMissingFromData attribute in <copy></h2>
+<p><a
name="FlexibleAssigns-AddsupportfortheignoreMissingFromDataattributeincopy"></a></p>
+<h2 id="add-support-for-the-ignoremissingfromdata-attribute-in-copy">Add
support for the ignoreMissingFromData attribute in
<code><copy></code></h2>
<p>The attached patch adds support for the following attributes in the BPEL
assign activity's copy operation: </p>
<ol>
<li>
Modified: websites/staging/ode/trunk/content/extensions/headers-handling.html
==============================================================================
--- websites/staging/ode/trunk/content/extensions/headers-handling.html
(original)
+++ websites/staging/ode/trunk/content/extensions/headers-handling.html Mon Dec
31 10:41:16 2012
@@ -28,7 +28,7 @@
<li class="">
<a href="/getting-ode.html">Getting ODE</a>
</li>
- <li class=" dropdown">
+ <li class="active dropdown">
<a href="/user-guide.html" class="dropdown-toggle"
data-toggle="dropdown" data-target="#">Documentation<b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="/userguide/">User Guide</a></li>
@@ -83,7 +83,8 @@
<div class="row">
<div class="span12">
- <p>There are several situations where one would want to access
headers form the wire format in their BPEL process. It could be to assign them
to another message and pass them around or to execute some business logic
that's header-dependent (often a bad idea but sometimes there's no choice). ODE
supports the manipulation of wire format headers in two different ways.</p>
+ <h2 id="overview">Overview</h2>
+<p>There are several situations where one would want to access headers form
the wire format in their BPEL process. It could be to assign them to another
message and pass them around or to execute some business logic that's
header-dependent (often a bad idea but sometimes there's no choice). ODE
supports the manipulation of wire format headers in two different ways.</p>
<p><a name="HeadersHandling-HeadersasAbstractMessageParts"></a></p>
<h3 id="headers-as-abstract-message-parts">Headers as Abstract Message
Parts</h3>
<p>In SOAP, message parts can be bound to a SOAP header. This requires to
define all the parts that you want to extract in the abstract message
definition and then create an appropriate binding to specify the parts that
actually go in the header. </p>
Modified: websites/staging/ode/trunk/content/extensions/iterable-foreach.html
==============================================================================
--- websites/staging/ode/trunk/content/extensions/iterable-foreach.html
(original)
+++ websites/staging/ode/trunk/content/extensions/iterable-foreach.html Mon Dec
31 10:41:16 2012
@@ -28,7 +28,7 @@
<li class="">
<a href="/getting-ode.html">Getting ODE</a>
</li>
- <li class=" dropdown">
+ <li class="active dropdown">
<a href="/user-guide.html" class="dropdown-toggle"
data-toggle="dropdown" data-target="#">Documentation<b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="/userguide/">User Guide</a></li>
@@ -83,11 +83,12 @@
<div class="row">
<div class="span12">
- <p>This extension simplifies a common usage pattern in which forEach
is used to iterate over a selected sequence of nodes.</p>
+ <h2 id="overview">Overview</h2>
+<p>This extension simplifies a common usage pattern in which forEach is used
to iterate over a selected sequence of nodes.</p>
<p>The common use case involves selecting a sequence of nodes, storing it in a
scope variable, and using forEach to iterate over that sequence, using the
current counter value to extract and operate on the indexed value from the
sequence. This extension captures the pattern in a form that's easier to
author and debug, by replacing counter with iterator and eliminating the use of
temporary variables.</p>
<p><a name="IterableForEach-ProcessingMultipleBranches-ForEach"></a></p>
<h2 id="processing-multiple-branches-foreach">Processing Multiple Branches -
ForEach</h2>
-<p>The <forEach> activity will execute its contained <scope> activity exactly
M times where M is the number of items in the <sequenceValue>.</p>
+<p>The <code><forEach></code> activity will execute its contained
<scope> activity exactly M times where M is the number of items in the
<sequenceValue>.</p>
<div class="codehilite"><pre><span class="nt"><forEach</span> <span
class="na">rangeName=</span><span class="s">"BPELVariableName"</span>
<span class="na">parallel=</span><span class="s">"yes|no"</span>
<span class="err">standard-attributes</span><span class="nt">></span>
standard-elements
Modified: websites/staging/ode/trunk/content/extensions/restful-bpel-part-i.html
==============================================================================
--- websites/staging/ode/trunk/content/extensions/restful-bpel-part-i.html
(original)
+++ websites/staging/ode/trunk/content/extensions/restful-bpel-part-i.html Mon
Dec 31 10:41:16 2012
@@ -28,7 +28,7 @@
<li class="">
<a href="/getting-ode.html">Getting ODE</a>
</li>
- <li class=" dropdown">
+ <li class="active dropdown">
<a href="/user-guide.html" class="dropdown-toggle"
data-toggle="dropdown" data-target="#">Documentation<b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="/userguide/">User Guide</a></li>
@@ -83,7 +83,8 @@
<div class="row">
<div class="span12">
- <div class="alert alert-warning">
+ <h2 id="restful-bpel-i">RESTful BPEL (I)</h2>
+<div class="alert alert-warning">
This feature is not yet implemented in ODE. This is a proposal and is
subject to change based on feedback, implementation experience, etc.
</div>
Modified:
websites/staging/ode/trunk/content/extensions/restful-bpel-part-ii.html
==============================================================================
--- websites/staging/ode/trunk/content/extensions/restful-bpel-part-ii.html
(original)
+++ websites/staging/ode/trunk/content/extensions/restful-bpel-part-ii.html Mon
Dec 31 10:41:16 2012
@@ -28,7 +28,7 @@
<li class="">
<a href="/getting-ode.html">Getting ODE</a>
</li>
- <li class=" dropdown">
+ <li class="active dropdown">
<a href="/user-guide.html" class="dropdown-toggle"
data-toggle="dropdown" data-target="#">Documentation<b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="/userguide/">User Guide</a></li>
@@ -83,10 +83,10 @@
<div class="row">
<div class="span12">
- <div class="alert alert-warning">
+ <h2 id="restful-bpel-ii">RESTful BPEL (II)</h2>
+<p><div class="alert alert-warning">
This feature is not yet implemented in ODE. This is a proposal subject to
feedback, implementation experience, etc.
-</div>
-
+</div></p>
<p><a name="RESTfulBPEL,PartII-UseCases"></a></p>
<h3 id="use-cases">Use Cases</h3>
<p><em>Use case 1</em>: A client needs to process <em>foo</em>, which it does
by creating a new resource which it can operate on. The client starts by making
a POST request to /foos. This results in a new resource, a response with status
code 201 (Created), relevant document and the Location header pointing to the
URL of the new resource (/foos/123). The client can then operate on the new
resource, e.g. reading its state at various points in time (GET), changing its
state (PUT), or even discarding it (DELETE).</p>
@@ -102,16 +102,16 @@
<p>The above deal specifically with resources, but in addition we will also
need a way to handle HTTP variables and query string parameters. We also
expect the process engine to take care of common protocol details, such as
status codes, redirection, cache control, content negotiation and encoding,
HEAD and OPTIONs requests, etc.</p>
<p><a name="RESTfulBPEL,PartII-Resources"></a></p>
<h3 id="resources">Resources</h3>
-<p>Resources are declared in a scope, and a scope may declare any number of
resources. A resource declaration consists of two properties, the resource
<em>name</em>, which we use to reference the resource, and a relative
<em>path</em> that denotes the relationship between this resource and other
resources. Once instantiated, the value of the resource is an absolute URL.</p>
+<p>Resources are declared in a scope, and a scope may declare any number of
resources. A resource declaration consists of two properties, the resource
<strong>name</strong>, which we use to reference the resource, and a relative
<strong>path</strong> that denotes the relationship between this resource and
other resources. Once instantiated, the value of the resource is an absolute
URL.</p>
<p>The process can use resources in two ways. It can reference a resource for
the purpose of receiving requests on that resource or a member of the
collection denoted by the resource. It can also access the value of the
resource (URL), for example, to send it as part of a message.</p>
<p>To access the value of the resource, we treat the resource as a read-only
variable with the type xsd:uri. Expressions can access the resource as they
would any other variable available in the scope, but cannot modify (assign to)
its value. For that reason, all resources declared in a scope must have unique
name and in addition no variable and resource declared in the same scope may
have the same name.</p>
<p>A resource that specifies no path (or the empty path) will be instantiated
using a URL unique to that process instance. A resource that specifies a static
path will be instantiated by appending that path to the instance URL. A
resource that specifies a path relative to another resource will be
instantiated by appending that path to the URL of the other resource. We use
the $ notation to reference another resource, so the path $foo/bar will append
/bar to the URL denoted by the resource $foo.</p>
<p><a name="RESTfulBPEL,PartII-Recievingrequests"></a></p>
<h3 id="recieving-requests">Recieving requests</h3>
-<p>To expose themselves as resources, the receive activity and event handler
introduce four new properties. The <em>method</em> property specifies the HTTP
method to accept, and the semantics of each HTTP method are described below.
The <em>resource</em> property references a resource declaration available in
the scope.</p>
-<p>The <em>instantiateResource</em> property is true if the resource is
instantiated by the receive activity or event handler, and false if the
resource must be instantiated before the activity executes. This property can
only be set to true when using the POST method, and is always true for the
instantiating activity of the process.</p>
+<p>To expose themselves as resources, the receive activity and event handler
introduce four new properties. The <strong>method</strong> property specifies
the HTTP method to accept, and the semantics of each HTTP method are described
below. The <strong>resource</strong> property references a resource declaration
available in the scope.</p>
+<p>The <strong>instantiateResource</strong> property is true if the resource
is instantiated by the receive activity or event handler, and false if the
resource must be instantiated before the activity executes. This property can
only be set to true when using the POST method, and is always true for the
instantiating activity of the process.</p>
<p>When instantiateResource is false, the resource is instantiated first and
the activity receives requests on that URL. When instantiateResource is true,
the resource value is calculated and the activity receives requests on that
URL. Once received, the resource is instantiated by appending a unique
identifier to that URL. For example, the receive activity listens on the URL
/foos, and upon receipt instantiates the resource to the URL /foos/123. In
addition, the corresponding reply activity will set the status code to 201
(Created) and set the Location header to the resource URL.</p>
-<p>The <em>resourceIdentity</em> activity names a variable that will be set to
the member identity when receiving requests on behalf of a collection resource.
When used in event handlers, the variable is implicitly defined in the implicit
scope of the event handler and has the type xsd:string.</p>
+<p>The <strong>resourceIdentity</strong> activity names a variable that will
be set to the member identity when receiving requests on behalf of a collection
resource. When used in event handlers, the variable is implicitly defined in
the implicit scope of the event handler and has the type xsd:string.</p>
<p>For example, if the resource is /foos/123/bars and the resourceIdentity is
set to bar, then the activity will receive requests on the URL
/foos/123/bars/{bar}, and the last part of the request URL path (the member
identity {bar}) is assigned to the value of the variable bar.</p>
<p><a name="RESTfulBPEL,PartII-POST"></a></p>
<h4 id="post">POST</h4>
@@ -140,8 +140,8 @@
<p>Both receive and reply activities have access to an implicit message part
called bodythat contains the internal representation of the document entity.
Receive activities have access to an implicit message part called params,
instantiated from the query string parameters. The XML representation of this
part consists of the element Parameters, which maps query string parameters as
follows:</p>
<ul>
<li>foo -- Maps to the element foo.</li>
-<li>foo[bar](bar.html) -- Maps to the element bar contained in the parent
element foo.</li>
-<li>foo[](.html) -- Each value is mapped to an element called foo in the
parent element foos.</li>
+<li>foo[bar] -- Maps to the element bar contained in the parent element
foo.</li>
+<li>foo[] -- Each value is mapped to an element called foo in the parent
element foos.</li>
</ul>
</div>
</div>
![http://ode.apache.org/img/ode-logo.png"](http://ode.apache.org/img/ode-logo.png"){kind=link}