Somehow DB got into this situation again (identical stack traces). I end-up removing (commenting out) @Version field from PSLBase class and now it works (without any changes to DB).
I think it points quite conclusively that something is not right with the way @Version field influence enhanced code. I will be more then happy to admit that I am doing something wrong, but I would like to know what exactly I am doing wrong. Andrei -- View this message in context: http://n2.nabble.com/Strange-%22ClassCast%22-Exception-%28and-even-stranger-way-it-disappear%29-tp2491173p2492567.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
