[
https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin....
]
Scott Marlow commented on WFLY-8954:
------------------------------------
Except for the datasource definitions, is there anything else Oracle specific in the test
case?
Obviously, there is something different on weblogic versus WildFly, because you are
reporting this issue. I have not yet heard of any application compatibility differences
when it comes to the weblogic JPA container versus the WildFly JPA container but that is
always a possibility. As you point out, the difference could be in the (JTA) transaction
managers.
If you like, you could enable TRACE logging for the JPA container, which should show a bit
more of what is going on. You could also enable the transaction manager TRACE logging
also, which can be verbose but useful when combined with the JPA trace logging. [Example
of enabling logging is
here|https://docs.jboss.org/author/display/WFLY10/JPA+Reference+Guide#JPA...].
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)