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

[NUNO GODINHO DE MATOS (Jira)]

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

NUNO GODINHO DE MATOS edited comment on WFLY-8954 at 11/20/19 3:07 AM:
-----------------------------------------------------------------------

Last time I checked the lastest version of eclipselink the oncussess bug still stood.
So in Widlfly13.0.Final which is the version we currently use, we still need to apply the patch proposed above to work-around the issue.

I am not sure, but I have the impression that It would be good if the wildfly base code itself would get patched, since we have that just by tweaking the wildfly JAR to integrate with eclipselink the issue can be resolved.

This would have the benefit that if the patch is 100% done on eclipselink, wildfly with eclipselink integration  will (theoretically) work only for very future versions of eclipselink still be released. If the eclipselink library is patched instead as discussed in this thread, than widlfly and eclipselink will cooperate properly even for older version of eclipselink in widepsread use. 

For us it is clear, that whenever we try to use a newer release of wildfly, we always have to patch ourselves the wildfly jar to integrate with eclipselink...

Thanks


was (Author: nuno.godinhomatos):
Last time I checked the lastest version of eclipselink the oncussess bug still stood.
So in Widlfly13.0.Final which is the version we currently use, we still need to apply the patch proposed above to work-around the issue.

I am not sure, but I have the impression that It would be good if the wildfly base code itself would get patched, since we have that just by tweaking the wildfly JAR to integrate with eclipselink the issue can be resolved.

This would have the benefit that wildfly with eclipselink integration would not be patched just for very future version of eclipselink...

We will continue apply the same patch over and over again, whenever we move wildfly version forward.
Thanks

> 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
>            Priority: Major
>
> 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.13.8#713008)