Andreas,
I think it's about time to create a bug report at http://bugzilla.exolab.org.
Having said that, reading your analysis it seems to me that the date conversion
issue could well be the cause for your problems. WHat surprises me is that this
occurs on Oracle, as I have seen similar behaviour on mySQL only so far.
Can I hence please ask you to attach the following files to the newly created
bug report as well:
- information about version sof Oracle/Castor being used.
- JDO configuration file.
- a mapping file.
- A JUnit test case
- all entities classes
required to run your test and reply your problems.
Werner
On Mon, 20 Dec 2004 09:22:58 +0100, Andreas Vombach wrote:
>
>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
>
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-user
