Author: jbarrez Date: 2009-07-03 05:02:32 -0400 (Fri, 03 Jul 2009) New Revision: 5206 Modified: jbpm4/trunk/modules/devguide/src/main/docbook/en/modules/ch14-SpringIntegration.xml Log: Changed Spring doc after review from Andries Modified: jbpm4/trunk/modules/devguide/src/main/docbook/en/modules/ch14-SpringIntegration.xml =================================================================== --- jbpm4/trunk/modules/devguide/src/main/docbook/en/modules/ch14-SpringIntegration.xml 2009-07-03 08:55:23 UTC (rev 5205) +++ jbpm4/trunk/modules/devguide/src/main/docbook/en/modules/ch14-SpringIntegration.xml 2009-07-03 09:02:32 UTC (rev 5206) @@ -42,7 +42,7 @@ <programlisting> &lt;process-engine-context&gt; &lt;command-service&gt; - <emphasis role="bold">&lt;spring-transaction-interceptor current=&quot;true&quot; /&gt;</emphasis> + <emphasis role="bold">&lt;spring-transaction-interceptor /&gt;</emphasis> ... &lt;/command-service&gt; ... @@ -111,7 +111,9 @@ The scripting engine will look into all contexts from the bean named echoService. If you configured the ScriptManager as above, Spring will be the last context to search for. - A good practice is to use unique names for the beans. + You can also add a Spring bean to the Spring Application context + (eg IdentitySessionImpl with id <emphasis role="italic">identitySession</emphasis>) + and use it in the jBPM config (eg by adding &lt;env class=&quot;identitySession&quot; /&gt;) </para> </section>