Hi,
I have a little problem with the caching of castor:
There are two classes ClassA and ClassB both have a 1:1 relation
(ClassA.getClassB()). Both classes implements the timestampable interface
(for long transactions).
Now I load ClassB from the database, modify something and update the data.
=> OK
castor log: Castor: Loading myapp.ClassB (6)
Then I load ClassA with the reference to ClassB
castor log: Castor: Loading myapp.ClassB (6)
castor log: Castor: Loading myapp.ClassA (1)
If I now load ClassB from the database, modify something and update the
data. => NOK!!!
I got a org.exolab.castor.jdo.ObjectModifiedException: Timestamp mismatched!
Was there build a new instance when ClassA load ClassB as a reference? Where
in castor code is the decision: �Load object from cache or load object from
database�?
Database -> TransactionContext -> LockEngine -> Molder???
Stefan
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
