]
Nuno Godinho de Matos commented on WFLY-8954:
---------------------------------------------
Ok thanks for all the info. I will do as you said with using the master as the base for
the branch with this test. As for going forward with the fix I must admit I am curious to
play with this layer of code so I will experiment with it and let you know if am clueless
or make any relevant progress. But most likely I will not really be able to do this during
normal working days due to sone important tasks that take presence, although it's a
fact that this bug is having an impact and we have so called dirty business logic because
of it. And this must really go away... Ok i will report back to you soon. Kindest
regards.
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
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.