Author: vanto
Date: Fri Nov 23 18:16:33 2012
New Revision: 1413009
URL: http://svn.apache.org/viewvc?rev=1413009&view=rev
Log:
markup 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=1413009&r1=1413008&r2=1413009&view=diff
==============================================================================
--- ode/site/trunk/content/architectural-overview.mdtext (original)
+++ ode/site/trunk/content/architectural-overview.mdtext Fri Nov 23 18:16:33
2012
@@ -22,7 +22,7 @@ The key components of the ODE architectu
The BPEL compiler is responsible for the conversion of the source BPEL
artifacts (i.e. BPEL process documents, WSDLs, and schemas) into a compiled
representation suitable for execution. The output of the compiler is either a
"good" compiled representation, or a list of error messages indicating problems
with the source artefacts.
-The compiled BPEL representation generated by the compiler is an object model
similar in structure to the underlying BPEL process document. However, the
compiled representation has resolved the various named references present in
the BPEL (such as variable names), internalized the required WSDL and type
information, and generated various constructs ( e.g. default compensation
handlers). The compiled representation (typically a file with the .cbp
extension) is the sole artifact required by the BPEL runtime.
+The compiled BPEL representation generated by the compiler is an object model
similar in structure to the underlying BPEL process document. However, the
compiled representation has resolved the various named references present in
the BPEL (such as variable names), internalized the required WSDL and type
information, and generated various constructs (e.g. default compensation
handlers). The compiled representation (typically a file with the .cbp
extension) is the sole artifact required by the BPEL runtime.
<a name="ArchitecturalOverview-ODEBPELEngineRuntime"></a>
### ODE BPEL Engine Runtime
@@ -47,7 +47,7 @@ ODE Data Access Objects mediate the inte
For the OpenJPA/JDBC DAO implementation, the relational structure used to
provide the above is shown in TODO.
<a name="ArchitecturalOverview-ODEIntegrationLayers"></a>
-## ODE Integration Layers
+### ODE Integration Layers
The ODE BPEL Engine Runtime cannot exist in a vacuum: by itself it is
incapable of affecting any interaction with the outside world. For this it
relies on an the ODE Integration Layers (ILs). Integration Layers embed the
runtime in an execution environment. For example, there are integration layers
for AXIS2 and JBI. The fundamental function of an IL is to provide
communication channels for the runtime. The AXIS2 IL achieves this by using the
AXIS2 libraries to allow the runtime to communicate via Web Service
interactions. The JBI IL achieves this same goal by tying the runtime into the
JBI message bus.
