well, my org.exolab.castor.jdo.ObjectModifiedException problem:
I use a Date field which seems not to be fully propagated to Oracle (Date but not time) so this is likely to be the reason ...
also my persistence class implements org.exolab.castor.jdo.TimeStampable and has a dependent class.
Anyway I would like to understand a bit more what's going on behind the scenes:
The org.exolab.castor.jdo.engine.SQLEngine class throws the exception at line 880 of it's store method. (talking about castor 0.9.5.3)
It does it because it thinks it was modified during the transaction ...?
Thanks Andreas
PS: Should I put my Tomcat experience to the wiki to be easier to be found?
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-user
