Boris, We had exactly the same problem - our solution was to use two connections. One cached, one non-cached. We have the entire object that needs to be persisted, however, and if I remember correctly you said you only have the changes. That could be an issue.
Anyway, hope this is helpful - Margaret -----Original Message----- From: Boris Klug [mailto:[EMAIL PROTECTED]] Sent: Friday, October 04, 2002 9:21 AM To: [EMAIL PROTECTED] Subject: Re: [castor-dev] Long transactions - how to do it (again!) Hello! now I have long transaction running. I implemented TimeStampable for my objects and it works now. The problem is now the caching of the objects. When I set cache-type in the mapping for for my class to "none", the timestamp does not work any longer (like stated in the docs). If I enable caching, everything works well, but modification to objects by other applications outside castor are not recognized. So any hints? I need long transaction but I also have to modify the objects outside Castor. Clues? -- Dipl. Inform. Boris Klug, control IT GmbH, Germany ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
