Hi,
we adjusted our jbpm.cfg.xml to use DbPersistenceServiceFactory instead of
JtaDbPersistenceServiceFactory. This configuratoin works fine... (read on)
<jbpm-context>
| <service name="persistence">
| <factory>
| <bean name="persistence.factory"
|
class="org.jbpm.persistence.db.DbPersistenceServiceFactory">
|
| <field name="isTransactionEnabled">
| <false />
| </field>
|
| </bean>
| </factory>
| </service>
| <service name="tx" factory="org.jbpm.tx.TxServiceFactory" />
| </jbpm-context>
... (continued) UNTIL you want to user the JBPM varmapping to store your
Hibernate LongIdInstances. There are some random -or at least confusing-
runtime behaviours when using Hibernate as JPA provider as well as JBPM
persistence engine. At least there is some confusion regarding responsibility
for the persisting of the LongIdInstaces between both Hibernate configurations.
We therefore went over to use TopLink as the JPA provider for our EJB3 Entity
Beans and keeping Hibernate as JBPM configuration.
HTH
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058605#4058605
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058605
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
