Author: buildbot
Date: Mon Dec 31 17:19:37 2012
New Revision: 844435
Log:
Staging update by buildbot for ode
Modified:
websites/staging/ode/trunk/content/ (props changed)
websites/staging/ode/trunk/content/developerguide/architectural-overview.html
Propchange: websites/staging/ode/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Dec 31 17:19:37 2012
@@ -1 +1 @@
-1427184
+1427186
Modified:
websites/staging/ode/trunk/content/developerguide/architectural-overview.html
==============================================================================
---
websites/staging/ode/trunk/content/developerguide/architectural-overview.html
(original)
+++
websites/staging/ode/trunk/content/developerguide/architectural-overview.html
Mon Dec 31 17:19:37 2012
@@ -101,7 +101,7 @@
<h3 id="ode-bpel-engine-runtime">ODE BPEL Engine Runtime</h3>
<p>The ODE BPEL Engine Runtime ("runtime") is found in the bpel-runtime module
and provides for the execution of compiled BPEL processes. The runtime handles
the dirty work of process execution by providing implementations of the various
BPEL constructs. The runtime also implements the logic necessary to determine
when a new instance should be created, and to which instance an incoming
message should be delivered. Finally, the runtime implements the Process
Management API that is used by user tooling to interact with the engine.</p>
<p>To achieve reliable execution of processes in unreliable environments, the
runtime relies on Data Access Objects (DAOs) to provide persistence facilities.
The implementation of these DAOs can be customized, but is typically provided
by a transactional relational database. The DAOs are described in more detail
in the next section.</p>
-<p>The runtime implementation of BPEL constructs at the instance level is via
ODE's Java Concurrent Objects (<a href="jacob.html">JaCOb</a>) framework. <a
href="jacob.html">JaCOb</a> provides an application-level concurrency mechanism
(i.e. it does not rely on threads) and a transparent mechanism for interrupting
execution and persisting execution state. <a href="jacob.html">JaCOb</a> is in
very large part a Java implementation of the Actors [<a
href="bibliography.html#agha86">Agha</a>] concurrency model and shares many
features with process algebras such as π-calculus. Essentially, <a
href="jacob.html">JaCOb</a> provides a persistent virtual machine for executing
BPEL constructs.</p>
+<p>The runtime implementation of BPEL constructs at the instance level is via
ODE's Java Concurrent Objects (<a href="jacob.html">JaCOb</a>) framework. <a
href="jacob.html">JaCOb</a> provides an application-level concurrency mechanism
(i.e. it does not rely on threads) and a transparent mechanism for interrupting
execution and persisting execution state. <a href="jacob.html">JaCOb</a> is in
very large part a Java implementation of the Actors [<a
href="/bibliography.html#agha86">Agha</a>] concurrency model and shares many
features with process algebras such as π-calculus. Essentially, <a
href="jacob.html">JaCOb</a> provides a persistent virtual machine for executing
BPEL constructs.</p>
<p><a name="ArchitecturalOverview-ODEDataAccessObjects"></a></p>
<h3 id="ode-data-access-objects">ODE Data Access Objects</h3>
<p>ODE Data Access Objects mediate the interaction between the BPEL Engine
Runtime and an underlying data store. Typically the data store is a JDBC
relational database: in this case, the DAOs is implemented via the OpenJPA data
access library. It is possible to create custom DAO implementations that employ
a mechanism other than JDBC to achieve persistence, although no such
implementation is provided. The BPEL Engine Runtime requires DAO objects to
deal with the following persistence issues:</p>
