[jboss-user] [jBPM] New message: "Re: jBPM 4.3 and Spring integration - multiple transaction managers"

Patricia B do-not-reply at jboss.com
Wed Mar 17 21:38:13 EDT 2010

User development,

A new message was posted in the thread "jBPM 4.3 and Spring integration - multiple transaction managers":


Author  : Patricia B
Profile : http://community.jboss.org/people/patriciab

Thank you for your reply.
I debugged the issue, and the problem seems to be on the SpringContext.java (line 60 I think), when it loads Spring beans from the context. In my case, there are 2 implementations for transaction manager. So, when running the app, SpringContext finds more than one transaction managers defined on the context, it takes the first one that it comes on the array, but gives me the warning I posted originally. 
The fix I see here, is to be able to specify which Spring bean name to load when there are multiple transaction managers defined on the context.
If you have a different solution for this problem, I appreciate it.
Below is a snippet from my context.xml and jbpm.cfg.xml:
<!-- context.xml ---->
<bean id="transactionManager"
<bean id="SisStageTransactionManager"
<bean id="springHelper" class="org.jbpm.pvm.internal.processengine.SpringHelper">
       <property name="jbpmCfg" value="jbpm4/jbpm.cfg.xml"/>
<bean id="processEngine" factory-bean="springHelper" factory-method="createProcessEngine" />

<!-- jbpm.cfg.xml ---->
    <import resource="jbpm.default.cfg.xml" />
    <import resource="jbpm.businesscalendar.cfg.xml" />
    <import resource="jbpm.tx.spring.cfg.xml" />
    <import resource="jbpm.jpdl.cfg.xml" />
    <import resource="jbpm.identity.cfg.xml" />
    <import resource="jbpm.jobexecutor.cfg.xml" />
    <import resource="jbpm.default.scriptmanager.xml" />
<!-- context.xml ---->


To reply to this message visit the message page: http://community.jboss.org/message/532650#532650

More information about the jboss-user mailing list