[seam-issues] [JBoss JIRA] (SEAMTRANSACTION-16) Conversation scoped EntityManager should enlist into the JTA independently of EntityManager invocation when invoking a @Transactional method
Adriano Scheffer (JIRA)
jira-events at lists.jboss.org
Sat Mar 3 13:30:36 EST 2012
Adriano Scheffer created SEAMTRANSACTION-16:
Summary: Conversation scoped EntityManager should enlist into the JTA independently of EntityManager invocation when invoking a @Transactional method
Project: Seam Transaction
Issue Type: Bug
Affects Versions: 3.1.0.Final
Environment: Windows 7, JBoss AS 6 / JBoss AS 7.1 / JBoss AS 7.1.1-SNAPSHOT
Reporter: Adriano Scheffer
Assignee: Stuart Douglas
A Conversation scoped EntityManager should be enlisted into the current JTA (flushing the persistence context), when joining a method annotated with @Transactional.
This is possibly a problem with the TransactionInterceptor, which does not invoke transaction.enlist method.
Just for reference:
7.9.1 Container Responsibilities:
For stateful session beans with extended persistence contexts:
When a business method of the stateful session bean is invoked, if the stateful session bean uses container managed transaction demarcation, and the entity manager is not already associated with the current JTA transaction, the container associates the entity manager with the current JTA transaction and calls EntityManager.joinTransaction.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues