[
https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin....
]
Tomas Kraus commented on WFLY-8954:
-----------------------------------
I made changes to implement JTA 1.1 TransactionSynchronizationRegistry in EclipseLink
master branch, see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=526419 for details. It
would be good if you can test next
http://www.eclipse.org/eclipselink/downloads/nightly.php (7th dec 2017 and later) and give
us feedback. Also, if we'll make backport into 2.7. and 2.6 branches, you can base
your changes on extending org.eclipse.persistence.transaction.JTA11TransactionController
class instead of current JTATransactionController.
Wildfly 10 with eclipselink Onscucess observer gets stale entity
----------------------------------------------------------------
Key: WFLY-8954
URL:
https://issues.jboss.org/browse/WFLY-8954
Project: WildFly
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 10.0.0.Final
Reporter: Nuno Godinho de Matos
Assignee: Scott Marlow
Fix For: 12.0.0.Alpha1
Hi,
In widlfly there seems to be an important issue concerning CDI events and observing these
events during onsuccess. At least while using eclipselink.
When using wildfly 10.0.0.Final together with eclipselink, if an application modifies an
entity A, fires an event stating entity A has been modified, and an observer consumes this
event during transaction success.
Then the observer will be working with stale entities that do not reflect the
modifications done to the entity.
A sample application for this issue is available in:
https://github.com/99sono/wildfly10-observe-on-success-stale-entity
The widlfly configuration xml for the sample application, is available in the application
itself, as can be seen in the readme documentation.
Many thanks for taking a look.
Kindest regards.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)