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

[ https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin.... ] Nuno Godinho de Matos commented on WFLY-8954: --------------------------------------------- Hi Scott, I still have not had the time to dedicate to this task. I have been prioritizing some other work, since for the time being in relation to this bug, on the instances where the phenomena has taken place, we are doing a "dirty" entitymanager.referesh(myStaleEntity), as work-around. This work-around is useless if one is clueless as to what entity may have been changed in a business transaction, but out of luck, we do know the instances that we are getting served stale. I hope to be able to dedicate some hours to this next week. By the way, I must give you guys compliements on the JBOSS CLI. The CLI is really fast. We have written python/jython based create domain script for our business configuration (e.g. dynamically produce wildfly CLI based on desired configuration settings - datasources, jms, etc...) and I must say the speed with which a new standalone domain can get created and then finally configured via CLI is incredible. I was not expecting the CLI to be so fast configuring queues, factories, datasources. Incredible. So big compliments! Kindest regards. -- This message was sent by Atlassian JIRA (v7.2.3#72005)