[weld-issues] [JBoss JIRA] Commented: (CDITCK-170) TransactionalObserversTest uses bean managed transactions and cannot test propagation
[
https://jira.jboss.org/browse/CDITCK-170?page=com.atlassian.jira.plugin.s...
]
David Allen commented on CDITCK-170:
------------------------------------
Why is a current transaction suspended when a method on another BMT is invoked? This
transaction should propagate to all invocations of EJBs and resource managers.
There appears to be something wrong here since even code to check the status of the
transaction on the first BMT is failing to detect that the transaction has been set to
rollback only, perhaps because there are indeed multiple transactions involved?
TransactionalObserversTest uses bean managed transactions and cannot
test propagation
-------------------------------------------------------------------------------------
Key: CDITCK-170
URL: https://jira.jboss.org/browse/CDITCK-170
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Marius Bogoevici
Assignee: David Allen
Fix For: 1.0.2.Final, 1.1.0.CR1
org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest uses
two BMT stateless beans: DogAgent and DogTrainer.
However,when a BMT business method is invoked, the existing transaction is suspended,
therefore the observer methods will be executed outside the scope of the transaction in
which the event has been fired.
Also, when the transaction is rolled back b/c of the observer setting the flag during
commit(), we expect the commit method to throw a RollbackException.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira