[jboss-user] [JBoss jBPM] - Re: Lock problems after migrating to JBPM 3.2 and Seam 2.0

[chawax]

What you say could have been a reason for my problem, but when I remove process.signal() it doesn't leave the node :( So it looks like signalling is still needed. Anyway, I couldn't understand how it could work : you can leave a node on many transitions, so you have to tell which one the process should take and you can do it using process.signal(). But what you say is true for an action binded to a transition. Thanks anyway, you gave me hope a few minutes lol

By the way, do you see something something in my jbpm.cfg.xml file ?

<jbpm-configuration>
  |   <jbpm-context>
  |     <service name="persistence">
  |        <factory>
  |           <bean class="org.jbpm.persistence.db.DbPersistenceServiceFactory">
  |              <field name="isTransactionEnabled"><false/></field>
  |           </bean>
  |        </factory>
  |     </service>
  |     <service name="message" factory="org.jbpm.msg.db.DbMessageServiceFactory" />
  |     <service name="scheduler" factory="org.jbpm.scheduler.db.DbSchedulerServiceFactory" />
  |     <service name="logging" factory="org.jbpm.logging.db.DbLoggingServiceFactory" />
  |     <service name="authentication" factory="org.jbpm.security.authentication.DefaultAuthenticationServiceFactory" />
  |     <service name="tx" factory="org.jbpm.tx.TxServiceFactory" />
  |   </jbpm-context>
  | </jbpm-configuration>

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086473#4086473

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086473