I might add that you could add a try/catch/finally: use a transaction on the first operation in the try block that can be rolled back if a succeeded flag is false in the finally block; after the 2nd operation in the try block the succeeded gets set to true; and if you use the referred pattern in the blog above on the 2nd operation, you might want to include pre-conditions and the operation to be performed (in other words, if it's a banking operation, you want to know that you expected the amount to be x before you add y).
On Jul 10, 9:15 pm, Didier Durand <durand.did...@gmail.com> wrote: > Hi, > > Have a look at this to understand the > issues:http://blog.notdot.net/2009/9/Distributed-Transactions-on-App-Engine > > regards > > didier > > On Jul 10, 11:09 pm, mscwd01 <mscw...@gmail.com> wrote: > > > > > > > > > Hey > > > I'm using JDO and need to update two entities both of which reside in > > their own entity group. As I cannot use a transaction, I'd like to > > determine how others achieve this. It is imperative that both entities > > are updated or none at all. > > > Thanks -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
