[jbpm-commits] JBoss JBPM SVN: r5927 - jbpm3/branches/jbpm-3.2-soa/modules/userguide/src/main/docbook/en/modules.

[do-not-reply at jboss.org]

Author: alex.guizar at jboss.com
Date: 2009-12-08 22:00:01 -0500 (Tue, 08 Dec 2009)
New Revision: 5927

Modified:
   jbpm3/branches/jbpm-3.2-soa/modules/userguide/src/main/docbook/en/modules/persistence.xml
Log:
minor edit to userguide persistence chapter

Modified: jbpm3/branches/jbpm-3.2-soa/modules/userguide/src/main/docbook/en/modules/persistence.xml
===================================================================
--- jbpm3/branches/jbpm-3.2-soa/modules/userguide/src/main/docbook/en/modules/persistence.xml	2009-12-08 14:25:34 UTC (rev 5926)
+++ jbpm3/branches/jbpm-3.2-soa/modules/userguide/src/main/docbook/en/modules/persistence.xml	2009-12-09 03:00:01 UTC (rev 5927)
@@ -46,10 +46,8 @@
   jbpmContext.close();
 }</programlisting>     
 
-    <para>In what follows, we suppose that the configuration includes a persistence 
-      service similar to this one (as in the example configuration file 
-      <literal>src/config.files/jbpm.cfg.xml</literal>):
-    </para>
+    <para>In the following sections, the configuration is assumed to include a persistence 
+      service as shown below.</para>
 
     <programlisting>&lt;jbpm-configuration&gt;
 
@@ -59,8 +57,10 @@
   &lt;/jbpm-context&gt;
   ...
 &lt;/jbpm-configuration&gt;</programlisting>
+    </section>
 
-    </section><section id="conveniencemethodsonjbpmcontext"><title>Convenience methods on JbpmContext</title>
+    <section id="conveniencemethodsonjbpmcontext">
+    <title>Convenience methods on JbpmContext</title>
 
     <para>The three most common persistence operations are:
       <itemizedlist>
@@ -135,32 +135,28 @@
 }</programlisting>
 
     <para>Just as background information, the next part is an explanation of how jBPM manages 
-      the persistence and uses hibernate.
+      the persistence through Hibernate.
     </para>
 
-    <para>The <literal>JbpmConfiguration</literal> maintains a set of 
-      <literal>ServiceFactory</literal>s.  The service factories are configured in the 
-      <literal>jbpm.cfg.xml</literal> as shown above and instantiated lazy.  The 
-      <literal>DbPersistenceServiceFactory</literal> is only instantiated the first time 
-      when it is needed. After that, service factories are maintained in the 
-      <literal>JbpmConfiguration</literal>.  A <literal>DbPersistenceServiceFactory</literal>
-      manages a hibernate <literal>SessionFactory</literal>.  But also the hibernate 
-      session factory is created lazy when requested the first time.
+    <para>The <literal>JbpmConfiguration</literal> maintains a list of 
+      <literal>ServiceFactory</literal> instances. The service factories are configured in 
+      <literal>jbpm.cfg.xml</literal> and instantiated as needed.
+      The <literal>DbPersistenceServiceFactory</literal> manages a Hibernate 
+      <literal>SessionFactory</literal>. The session factory is built on demand as well,
+      since not every operation in <literal>DbPersistenceServiceFactory</literal> requires it.
     </para>
 
     <figure id="persistence.api.image">
-      <title>The persistence related classes</title>
+      <title>Classes related to persistence</title>
       <mediaobject><imageobject><imagedata align="center" fileref="images/persistence.api.gif"/></imageobject></mediaobject>
     </figure>
     
     <para>During the invocation of <literal>jbpmConfiguration.createJbpmContext()</literal>, 
-      only the <literal>JbpmContext</literal> is created.  No further persistence related 
-      initializations are done at that time.  The <literal>JbpmContext</literal> manages 
-      a <literal>DbPersistenceService</literal>, which is instantiated upon first request. 
-      The <literal>DbPersistenceService</literal> manages the hibernate session.  Also the 
-      hibernate session inside the <literal>DbPersistenceService</literal> is created lazy.
-      As a result, a hibernate session will be only be opened when the first operation is 
-      invoked that requires persistence and not earlier.
+      only the <literal>JbpmContext</literal> is created. No further persistence related 
+      initializations are done at that time.  The <literal>JbpmContext</literal> maintains 
+      a sequence of <literal>Service</literal> instances, created as needed. 
+      The <literal>DbPersistenceService</literal> wraps a Hibernate session 
+      which is opened when the first persistence operation is performed.
     </para>
 
     </section><section id="managedtransactions"><title>Managed transactions</title>