Author: vanto
Date: Fri Nov 23 18:03:01 2012
New Revision: 1413003

URL: http://svn.apache.org/viewvc?rev=1413003&view=rev
Log:
markup fix.

Modified:
    ode/site/trunk/content/jacob.mdtext

Modified: ode/site/trunk/content/jacob.mdtext
URL: 
http://svn.apache.org/viewvc/ode/site/trunk/content/jacob.mdtext?rev=1413003&r1=1413002&r2=1413003&view=diff
==============================================================================
--- ode/site/trunk/content/jacob.mdtext (original)
+++ ode/site/trunk/content/jacob.mdtext Fri Nov 23 18:03:01 2012
@@ -1,4 +1,4 @@
-Title: JaCOb
+Title: JaCOb -- ODE's Virtual Processing Unit
 
 <a name="Jacob-Introduction"></a>
 ## Introduction
@@ -10,9 +10,9 @@ ODE's BPEL implementation relies on the 
 
 By rolling up these concerns in the framework, the implementation of the BPEL 
constructs can be simpler by limiting itself to implementing the BPEL logic and 
not the infrastructure necessary to support it.
 
-The approach we'll take in this tutorial is looking at the 
[#rational](#rational.html) of JaCOb and its [#concepts] first. Then we'll 
illustrate with one complete [example](#examples). But if you're a reverse 
reader, you can also decide to start with the [example](#example1).
+The approach we'll take in this tutorial is looking at the 
[rationale](#rationale) of JaCOb and its [concepts](#concepts) first. Then 
we'll illustrate with one complete [example](#example). But if you're a reverse 
reader, you can also decide to start with the [example](#example).
 
-<a name="Jacob-Rationalebehindthemodel"></a>
+<a name="rationale"></a>
 ## Rationale behind the model
 
 Let's start from the most classical example of all:
@@ -100,6 +100,7 @@ From a client standpoint, we've achieved
 
 Next step is adding links, fault handling/termination, compensation and event 
handlers and seeing that continue/listenOn is all you need. The last step is 
just adding implementation details.
     
+<a name="example"></a>
 ## JaCOb Example
     
 Consider the issue of persistence. Imagine a simplified and naive 
implementation of the BPEL constructs ```<sequence>```, ```<wait>```, and 
```<empty>```:
@@ -232,8 +233,8 @@ JaCOb aims to solve this problem by prov
 
 So JaCOb constructs help us in breaking the execution stack.
 
-<a name="Jacob-MainJacobConcepts="></a>
-## Main JaCOb Concepts =
+<a name="concepts></a>
+## Main JaCOb Concepts
 
 <a name="Jacob-Channels"></a>
 ### Channels


Reply via email to