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:
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.