[jboss-jira] [JBoss JIRA] (WFLY-8954) Wildfly 10 with eclipselink Onscucess observer gets stale entity

[Scott Marlow (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433665#comment-13433665 ] 

Scott Marlow commented on WFLY-8954:
------------------------------------

# Please look at [https://community.jboss.org/wiki/HackingOnWildFly]
# after you git clone [https://github.com/wildfly/wildfly], do a "git checkout -b WFLY-8954" 
# In your local wildfly folder, change into the wildfly folder and run "build.sh clean install" (or build.bat) to build the app server.
# change into the testsuite/compat folder and run "mvn clean install" (you need Apache Maven installed for this step) and that will run a minimal EclipseLink test.
# start making changes of your local copy of the  [https://github.com/wildfly/wildfly/tree/master/testsuite/compat/src/test/java/org/jboss/as/test/compat/jpa/eclipselink] folder, to reproduce the failure with EclipseLink
# Run "mvn clean install" again with your test changes and verify that your seeing the same error.
# Do a "git push origin WFLY-8954" to push your test code changes to github.

After that, we can discuss further how to try code changes to address the failure.  

One more thing, you need to agree that your code contributions be made under the terms of the MIT License, [http://www.opensource.org/licenses/mit-license.php]. Comment in response if you agree to these terms?


> 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)