Author: buildbot
Date: Fri Nov 23 09:48:24 2012
New Revision: 839278
Log:
Staging update by buildbot for ode
Modified:
websites/staging/ode/trunk/content/ (props changed)
websites/staging/ode/trunk/content/bpel-extensions.html
Propchange: websites/staging/ode/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Nov 23 09:48:24 2012
@@ -1 +1 @@
-1412792
+1412801
Modified: websites/staging/ode/trunk/content/bpel-extensions.html
==============================================================================
--- websites/staging/ode/trunk/content/bpel-extensions.html (original)
+++ websites/staging/ode/trunk/content/bpel-extensions.html Fri Nov 23 09:48:24
2012
@@ -81,65 +81,66 @@
<div class="row">
<div class="span12">
- <p>ODE extends the <a href="ws-bpel-2.0.html">WS-BPEL</a> in areas
that aren't covered by the spec. This page details these extensions.</p>
+ <h1 id="overview">Overview</h1>
+<p>ODE extends the <a href="ws-bpel-2.0.html">WS-BPEL</a> in areas that aren't
covered by the spec. This page details these extensions.</p>
<ul>
-<li><a href="#BPELExtensions-[ImplicitCorrelations]">[Implicit
Correlations]</a></li>
-<li><a href="#BPELExtensions-[ActivityFailureandRecovery]">[Activity Failure
and Recovery]</a></li>
-<li><a
href="#BPELExtensions-[ExtensionActivities&ExtensibleAssignOperations]">[Extension
Activities & Extensible Assign Operations]</a></li>
-<li><a href="#BPELExtensions-[XPathExtensions]">[XPath Extensions]</a></li>
-<li><a href="#BPELExtensions-[ExternalVariables]">[External Variables]</a></li>
-<li><a href="#BPELExtensions-[HeadersHandling]">[Headers Handling]</a></li>
-<li><a href="#BPELExtensions-[RESTfulBPEL,PartI]">[RESTful BPEL, Part
I]</a></li>
-<li><a href="#BPELExtensions-[RESTfulBPEL,PartII]">[RESTful BPEL, Part
II]</a></li>
-<li><a href="#BPELExtensions-[IterableForEach]">[Iterable ForEach]</a></li>
-<li><a href="#BPELExtensions-[FlexibleAssigns]">[Flexible Assigns]</a></li>
-<li><a href="#BPELExtensions-[ProcessContexts]">[Process Contexts]</a></li>
+<li><a href="#BPELExtensions-ImplicitCorrelations">Implicit
Correlations</a></li>
+<li><a href="#BPELExtensions-ActivityFailureandRecovery">Activity Failure and
Recovery</a></li>
+<li><a
href="#BPELExtensions-ExtensionActivities-ExtensibleAssignOperations">Extension
Activities & Extensible Assign Operations</a></li>
+<li><a href="#BPELExtensions-XPathExtensions">XPath Extensions</a></li>
+<li><a href="#BPELExtensions-ExternalVariables">External Variables</a></li>
+<li><a href="#BPELExtensions-HeadersHandling">Headers Handling</a></li>
+<li><a href="#BPELExtensions-RESTfulBPEL,PartI">RESTful BPEL, Part I</a></li>
+<li><a href="#BPELExtensions-RESTfulBPEL,PartII">RESTful BPEL, Part II</a></li>
+<li><a href="#BPELExtensions-IterableForEach">Iterable ForEach</a></li>
+<li><a href="#BPELExtensions-FlexibleAssigns">Flexible Assigns</a></li>
+<li><a href="#BPELExtensions-ProcessContexts">Process Contexts</a></li>
</ul>
-<p><a name="BPELExtensions-<a
href="implicitcorrelations.html">ImplicitCorrelations</a>"></a></p>
-<h2 id="implicit-correlations">[Implicit Correlations]</h2>
+<p><a name="BPELExtensions-ImplicitCorrelations"></a></p>
+<h2 id="implicit-correlations"><a href="implicitcorrelations.html">Implicit
Correlations</a></h2>
<p>BPEL process instances are stateful â therefore, a client interacting
with the BPEL engine must identify the particular instance with which it
intends to interact in all of its communications. The BPEL specification
defines a mechanism â <em>correlation</em> â which allows the process
designer to specify which parts of an incoming message (i.e. a message going
from a client to the BPEL server) should be used to identify the target process
instance. Correlation is a powerful mechanism â however it is a bit
complicated and relies on "in-band" message data to associate a messages with a
process instance.</p>
<p>To keep simple cases simple, ODE provides an alternative correlation
mechanism â <em>implicit correlation</em> â that automatically handles
correlation through "out-of-band" session identifiers. The mechanism is simple:
a unique session identifier is associated with every every partner link
instance. When a message is sent on a partner link, the session identifier is
sent along with the message. The recipient is then able to use the received
session identifier in subsequent communications with the process instance.
Messages received by the BPEL engine that have a session identifier are routed
to the correct instance (and partner link) by that session identifier.</p>
<p><a href="implicit-correlations.html">Read more</a></p>
-<p><a name="BPELExtensions-<a
href="activityfailureandrecovery.html">ActivityFailureandRecovery</a>"></a></p>
-<h2 id="activity-failure-and-recovery">[Activity Failure and Recovery]</h2>
+<p><a name="BPELExtensions-ActivityFailureandRecovery"></a></p>
+<h2 id="activity-failure-and-recovery"><a
href="activityfailureandrecovery.html">Activity Failure and Recovery</a></h2>
<p>There are several types of error conditions. In this document we introduce
a class of error condition called <em>failures</em>, distinct from
<em>faults</em>, and describe how failures are caught and handled by the
process engine.</p>
<p>For example, when the process is unable to perform DNS resolution to
determine the service endpoint, it generates a failure. An administrator can
fix the DNS server and tell the process engine to retry the activity. Had the
DNS error been reported as a fault, the process would either terminate or
require complex fault handling and recovery logic to proceed past this point of
failure.</p>
<p>In short, failures shields the process from common, non-terminal error
conditions while retaining simple and straightforward process definitions that
do not need to account for these error conditions.</p>
<p><a href="activity-failure-and-recovery.html">Read more</a></p>
-<p><a name="BPELExtensions-<a
href="extensionactivities&extensibleassignoperations.html">ExtensionActivities&ExtensibleAssignOperations</a>"></a></p>
-<h2 id="extension-activities-extensible-assign-operations">[Extension
Activities & Extensible Assign Operations]</h2>
+<p><a
name="BPELExtensions-ExtensionActivities-ExtensibleAssignOperations"></a></p>
+<h2 id="extension-activities-extensible-assign-operations"><a
href="extensionactivities-extensibleassignoperations.html">Extension Activities
& Extensible Assign Operations</a></h2>
<p>Apache ODE provides a plug-in architecture for custom activity
implementations and custom variable assignment logic. Such plug-ins can be
registered to ODE and can be used according to the WS-BPEL 2.0 extensibility
mechnisms (<code><extensionActivity></code> &
<code><extensionAssignOperation></code>).</p>
<p><a href="extension-activities-&-extensible-assign-operations.html">Read
more</a></p>
-<p><a name="BPELExtensions-<a
href="xpathextensions.html">XPathExtensions</a>"></a></p>
-<h2 id="xpath-extensions">[XPath Extensions]</h2>
+<p><a name="BPELExtensions-XPathExtensions"></a></p>
+<h2 id="xpath-extensions"><a href="xpathextensions.html">XPath
Extensions</a></h2>
<p>Apache ODE extends the default XPath coverage provided by the WS-BPEL
specification mostly by adding support for <a
href="http://www.w3.org/TR/xpath20/";>XPath 2.0</a> and by offering a few
utility extension functions to make some assignments easier.</p>
<p><a href="xpath-extensions.html">Read more</a></p>
-<p><a name="BPELExtensions-<a
href="externalvariables.html">ExternalVariables</a>"></a></p>
-<h2 id="external-variables">[External Variables]</h2>
+<p><a name="BPELExtensions-ExternalVariables"></a></p>
+<h2 id="external-variables"><a href="externalvariables.html">External
Variables</a></h2>
<p>External variables are an easy way to share data between the process and
external systems, by treating those independent entities as BPEL variables that
can be used in expressions and assignments. External variables may be records
stored in the database, REST resources, etc.</p>
<p><a href="external-variables.html">Read more</a></p>
-<p><a name="BPELExtensions-<a
href="headershandling.html">HeadersHandling</a>"></a></p>
-<h2 id="headers-handling">[Headers Handling]</h2>
+<p><a name="BPELExtensions-HeadersHandling"></a></p>
+<h2 id="headers-handling"><a href="headershandling.html">Headers
Handling</a></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 href="headers-handling.html">Read more</a></p>
-<p><a name="BPELExtensions-<a
href="restfulbpel,parti.html">RESTfulBPEL,PartI</a>"></a></p>
-<h2 id="restful-bpel-part-i">[RESTful BPEL, Part I]</h2>
+<p><a name="BPELExtensions-RESTfulBPEL,PartI"></a></p>
+<h2 id="restful-bpel-part-i"><a href="restfulbpel,parti.html">RESTful BPEL,
Part I</a></h2>
<p>Extends the invoke activity to handle RESTful Web services. This extension
uses BPEL variables of type xsd:uri and xsd:string instead of partner links,
and does away with the WSDL indirection, making it straightforward to develop
processes that use RESTful Web services. </p>
<p><a href="restful-bpel,-part-i.html">Read more</a></p>
-<p><a name="BPELExtensions-<a
href="restfulbpel,partii.html">RESTfulBPEL,PartII</a>"></a></p>
-<h2 id="restful-bpel-part-ii">[RESTful BPEL, Part II]</h2>
+<p><a name="BPELExtensions-RESTfulBPEL,PartII"></a></p>
+<h2 id="restful-bpel-part-ii"><a href="restfulbpel,partii.html">RESTful BPEL,
Part II</a></h2>
<p>Extends receive and onEvent to expose RESTful resources that. This
extension adds the ability to declare and instantiate resources, and specific
handling for the HTTP methods GET, POST, PUT and DELETE.</p>
<p><a href="restful-bpel,-part-ii.html">Read more</a></p>
-<p><a name="BPELExtensions-<a
href="iterableforeach.html">IterableForEach</a>"></a></p>
-<h2 id="iterable-foreach">[Iterable ForEach]</h2>
+<p><a name="BPELExtensions[IterableForEach"></a></p>
+<h2 id="iterable-foreach"><a href="iterableforeach.html">Iterable
ForEach</a></h2>
<p>Extends the <forEach> activity so that the counter variable iterates over
the items contained in a given sequence. This extension provides an
alternative and more dynamic way of generating M branches, where M is the size
of the binding sequence. The semantics of the <completionCondition> stays the
same, in that the loop is deemed to be complete if B out of the M branches
complete (successfully), where B is its actual value.</p>
<p><a href="iterable-foreach.html">Read more</a></p>
-<p><a name="BPELExtensions-<a
href="flexibleassigns.html">FlexibleAssigns</a>"></a></p>
-<h2 id="flexible-assigns">[Flexible Assigns]</h2>
+<p><a name="BPELExtensions-FlexibleAssigns"></a></p>
+<h2 id="flexible-assigns"><a href="flexibleassigns.html">Flexible
Assigns</a></h2>
<p>Extends the <assign> activity so that it can be made to either ignore or
insert data that is missing in the to-spec of a copy operation. This shortcut
allows users to handle what would normally be fault scenarios, in a more
graceful and intuitive way.</p>
<p><a href="flexible-assigns.html">Read more</a></p>
-<p><a name="BPELExtensions-<a
href="processcontexts.html">ProcessContexts</a>"></a></p>
-<h2 id="process-contexts">[Process Contexts]</h2>
+<p><a name="BPELExtensions-ProcessContexts"></a></p>
+<h2 id="process-contexts"><a href="processcontexts.html">Process
Contexts</a></h2>
<p>Extends BPEL and ODE to allow the circulation of transport metadata (like
security tokens, correlation keys, or tracing informations) from messages to
processes and then from processes to messages.</p>
<p><a href="process-contexts.html">Read more</a></p>
</div>
