Title: Message Title
|
|
Hi,
I'll try to make a simple version of the code, and I will share it with you as soon as I have it.
Meanwhile, I've realized that I might be trying to do something that is not supported. Just to make sure, I'd like to check with you the following points: # Is it allowed in a transactional observer to start a new transaction during the AFTER_SUCCESS, AFTER_FAILURE, AFTER_COMPLETION phase? I'm asking because when I have a look to the weld-jta code I don't see how this could be working and also because I've not been able to find any example with such a usage of transactional observers. # What would happen if the transactional observer were invoked during the BEFORE_COMPLETION phase and were starting a new transaction?
The exact behavior of transactional observers with respect to starting a new transaction is unclear. And I don't know if this is supported or / and recommended.
The parts of the code I have in mind is are : * org.jboss.weld.module.jta.TransactionalObserverNotifier::notifyTransactionObservers * org.jboss.weld.event.ObserverNotifier::notify
These methods are invoked when the event is fired. The synchronization callback is set in the method notifyTransactionObservers, which is called when an event is fired, and is never cleared. |
|
|
|
|
|
_______________________________________________
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues