jBPM and Spring - Spring Enterprise Recipes: A Problem Solution Approach - page 419

<process-engine-context>
<repository-service />
<repository-cache />
<execution-service />
<history-service />
<management-service />
<identity-service />
<task-service />
<command-service>
<retry-interceptor />
<environment-interceptor />
<spring-transaction-interceptor />
</command-service>
<script-manager default-expression-language="juel"
default-script-language="juel"
read-contexts="execution, environment, process-engine, spring"
write-context="">
<script-language name="juel"
factory="org.jbpm.pvm.internal.script.JuelScriptEngineFactory" />
</script-manager>
<authentication />
<id-generator />
<types resource="jbpm.variable.types.xml" />
<address-resolver />
<business-calendar>
<monday hours="9:00-12:00 and 12:30-17:00" />
<tuesday hours="9:00-12:00 and 12:30-17:00" />
<wednesday hours="9:00-12:00 and 12:30-17:00" />
<thursday hours="9:00-12:00 and 12:30-17:00" />
<friday hours="9:00-12:00 and 12:30-17:00" />
<holiday period="01/07/2008 - 31/08/2008" />
</business-calendar>
</process-engine-context>
<transaction-context>
<repository-session />
<db-session />
<message-session />
<timer-session />
<history-session />
<hibernate-session current="true" />
</transaction-context>
</jbpm-configuration>
By and large, this is a pretty standard configuration for jBPM. It specifies many things that are safe
defaults, and largely out of the scope of this topic. Mainly, the configuration tells jBPM which services
to bring up and defines some configuration for those services. Because we're integrating with Spring,
we modify the transaction-context element and the command-service element, as those are the
touch points with Spring. The hibernate-session element tells jBPM to reuse an existing Hibernate
session (the one we created with our Hibernate Session factory) instead of creating its own. The
spring-transaction-interceptor element is a special element to enable jBPM to defer to the
TransactionManager defined in our application context. Here again, jBPM integrates by delegating to
the Spring services, making for a very eloquent solution.