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/05 21:07:06 UTC
svn commit: r1417618 - /ode/site/trunk/content/architectural-overview.mdtext
Author: vanto
Date: Wed Dec 5 20:07:05 2012
New Revision: 1417618
URL: http://svn.apache.org/viewvc?rev=1417618&view=rev
Log:
link fix
Modified:
ode/site/trunk/content/architectural-overview.mdtext
Modified: ode/site/trunk/content/architectural-overview.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/architectural-overview.mdtext?rev=1417618&r1=1417617&r2=1417618&view=diff
==============================================================================
--- ode/site/trunk/content/architectural-overview.mdtext (original)
+++ ode/site/trunk/content/architectural-overview.mdtext Wed Dec 5 20:07:05 2012
@@ -16,7 +16,7 @@ The principal objective in the developme
The key components of the ODE architecture include the ODE BPEL Compiler, ODE BPEL Engine Runtime, ODE Data Access Objects (DAOs), ODE Integration Layers (ILs), and user tooling. A high-level depiction of the relationships between these components is shown in the Figure below. It can be summarized as: "The compiler converts BPEL documents into a form executable by the run-time, which executes them in a reliable fashion by relying on a persistent store accessible via the DAOs; the run-time executes in the context of an Integration Layer which connects the engine to the broader execution environment ( i.e. the "world").
-
+
<a name="ArchitecturalOverview-ODEBPELCompiler"></a>
### ODE BPEL Compiler