[jbpm-commits] JBoss JBPM SVN: r5987 - jbpm4/trunk/modules/devguide/src/main/docbook/en/modules.

[do-not-reply at jboss.org]

Author: jbarrez
Date: 2009-12-18 05:01:16 -0500 (Fri, 18 Dec 2009)
New Revision: 5987

Modified:
   jbpm4/trunk/modules/devguide/src/main/docbook/en/modules/ch02-Incubation.xml
   jbpm4/trunk/modules/devguide/src/main/docbook/en/modules/ch17-SpringIntegration.xml
Log:
Updated Spring and History-session-chain docs to reflect latest changes

Modified: jbpm4/trunk/modules/devguide/src/main/docbook/en/modules/ch02-Incubation.xml
===================================================================
--- jbpm4/trunk/modules/devguide/src/main/docbook/en/modules/ch02-Incubation.xml	2009-12-18 02:42:32 UTC (rev 5986)
+++ jbpm4/trunk/modules/devguide/src/main/docbook/en/modules/ch02-Incubation.xml	2009-12-18 10:01:16 UTC (rev 5987)
@@ -865,10 +865,10 @@
   	  is fired. Multiple custom implementations are possible as follows:
   	  <programlisting>
 &lt;transaction-context&gt;
-    &lt;history-session-chain&gt;
+    &lt;history-sessions&gt;
       &lt;object class=&quot;org.jbpm.test.historysessionchain.MyProcessStartListener&quot; /&gt;
       &lt;object class=&quot;org.jbpm.test.historysessionchain.MyProcessEndListener&quot; /&gt;
-    &lt;/history-session-chain&gt;
+    &lt;/history-sessions&gt;
   &lt;/transaction-context&gt;  	  
   	  </programlisting>
   	  The custom history sessions must be on the classpath when the jBPM configuration is parsed
@@ -885,6 +885,15 @@
 }  	  
   	  </programlisting>
   	</para>
+  	If you want to add the default history session implementation to your configuration, add the 
+  	following line to the transaction-context section:
+  	<programlisting>
+&lt;history-sessions&gt;
+      &lt;object class=&quot;org.jbpm.pvm.internal.history.HistorySessionImpl&quot; /&gt;
+&lt;/history-sessions&gt;  	
+  	</programlisting>
+  	If you are using the <emphasis role="bold">jbpm.default.cfg.xml</emphasis> import in your
+  	configuration, this default history session implementation is already configured as above.
   </section>
   
   <section>

Modified: jbpm4/trunk/modules/devguide/src/main/docbook/en/modules/ch17-SpringIntegration.xml
===================================================================
--- jbpm4/trunk/modules/devguide/src/main/docbook/en/modules/ch17-SpringIntegration.xml	2009-12-18 02:42:32 UTC (rev 5986)
+++ jbpm4/trunk/modules/devguide/src/main/docbook/en/modules/ch17-SpringIntegration.xml	2009-12-18 10:01:16 UTC (rev 5987)
@@ -80,22 +80,18 @@
 		The Spring integration provides a special context, which is added to
 		the set of contexts where the jBPM engine will look for beans.
 		Using this SpringContext, it is now possible to retrieve beans from the 
-		Spring Application Context. For the Spring context to be known, a 
-		SpringConfiguration must be created. This class extends the JbpmConfiguration 
-		but will add itself as a context. The single constructor take the location of the jBPM configuration.
-		
+		Spring Application Context. The jBPM process engine can be configured in a Spring 
+		applicationContext.xml as follows:		
 		<programlisting>
-	&lt;bean id=&quot;jbpmConfiguration&quot; class=&quot;org.jbpm.pvm.internal.cfg.SpringConfiguration&quot;&gt;
-   		&lt;constructor-arg value=&quot;be/inze/spring/demo/jbpm.cfg.xml&quot; /&gt;
-	&lt;/bean&gt;
-		</programlisting>
-	</para>	
-	
-	<para>
-	Using this configuration, a ProcessEngine can be created:
-	   <programlisting>
-&lt;bean id=&quot;processEngine&quot; factory-bean=&quot;jbpmConfiguration&quot; factory-method=&quot;buildProcessEngine&quot; /&gt;
+  <bean id="springHelper" class="org.jbpm.pvm.internal.processengine.SpringHelper">
+    <property name="jbpmCfg" value="org/jbpm/spring/jbpm.cfg.xml"></property>
+  </bean>
+
+  <bean id="processEngine" factory-bean="springHelper" factory-method="createProcessEngine" />
     </programlisting>
+    Note that the <emphasis role="bold">jbpmCfg</emphasis> property for the SpringHelper is optional.
+    If a default jbpm.cfg.xml exists on the classpath (ie not in some package), this line can
+    be removed.
 	</para>
 	
 	<para>