This one time, at band camp, Mutchler, Scott said: MS >I want to be able to call the save() method below once and persist the object to the database. Then I want to be able to update [outside any transaction] the object and call save() again to persist it again. Do I really have to change everything on the object between a begin() and commit() for it to be persisted? Isn't this the point of the TimeStampable interface to allow Castor to do dirty checking on objects updated outside a transaction?
As I understand what you're describing it is two separate transations. No, you don't need to change everything on the object graph within the space of a single transaction. Yes, the TimeStampable interface is designed for that. For a more detailed answer and an example to your questions, please see http://castor.exolab.org/long-transact.html for information on long transactions. MS > MS >Also, how do I change the XML mapping to allow automatic persistence of child objects? Here is my mapping file: For an example, please see the code for the examples in src/examples/jdo. -- perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");' ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
