No, the JPA-managed transaction is getting this error. And it is not an OptimisticLockException, but I am getting stale data on the next access. This sounds like a bug to me.
Ulrich
[Message sent by forum member 'ulim' (ulim)]
http://forums.java.net/jive/thread.jspa?messageID=242300