[jbpm-dev] [Design of JBoss jBPM] - Transaction interceptor changes
heiko.braun@jboss.com
do-not-reply at jboss.com
Fri Jun 19 07:07:52 EDT 2009
Most recent TX interceptor changes, break the console and the deployer:
| Caused by: org.jbpm.api.JbpmException: invalid transaction state: STATUS_ACTIVE
| at org.jbpm.pvm.internal.tx.jta.JtaTransactionInterceptor.execute(JtaTransactionInterceptor.java:60)
| at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:54)
| at org.jbpm.pvm.internal.repository.RepositoryServiceImpl.createProcessDefinitionQuery(RepositoryServiceImpl.java:77)
| at org.jbpm.integration.console.ProcessManagementImpl.getProcessDefinitions(ProcessManagementImpl.java:54)
| ... 45 more
|
|
Basically you cannot run within a provided transaction context (like ejb REQUIRED semantics).
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238746#4238746
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238746
More information about the jbpm-dev
mailing list