[
https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin....
]
Nuno Godinho de Matos commented on WFLY-8954:
---------------------------------------------
Hi,
So the pull that you have mentioned has been done.
You can compare the diff in relation to the 10.x branch which I used under:
https://github.com/99sono/wildfly/compare/10.x...99sono:WFLY-8954
I have needed to add to the pom.xml a dependency on.
{panel}
<dependency>
<!-- FIXME:
This library is added to give access to import
javax.enterprise.event.Event
The appropriate dependency to use for this that is already managed in a
parent pom is no known so for now we put this.
-->
<groupId>javax</groupId>
<artifactId>javaee-api</artifactId>
<scope>provided</scope>
<version>7.0</version>
</dependency>
{panel}
Which I imagine you will not like for multiple reasons.
- You do not manage artifact versions at this level
- You porbably have a better dependency to include to give access to the Event api
etc...
I also re-wrote the jndi dump metho I found on the sample test.
I thought the method could be cute to carry around on other contexts, I will probably be
using it myself elsewhere.
Other than that, I did not make any attempt to fix the issue on the wildfly base code.
I would have to study you sugestion for this, and I suspect that you want in any case for
someone from the narayana guys to look at this.
Please let me know if you are ok with this.
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.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)