Twig-Persist is GAE only. JDO is useful for when you want to build a GWT app that could either run against an RDBMS, GAE, or EC2. With JDO, you get more deployment choices.
However, the down side is all the extra coding associated with implementing the DTO pattern which is usually the answer to the incompatibility problem between JDO and GWT-RPC. I go into more detail on this in my http://www.dynamicalsoftware.com/gwt presentation. The extra code disadvantage to maintaining two sets of object hierarchies (client and server) gets mitigated when using MDSD techniques. Also, take a look at GeDA and simple-object-assembler. On Apr 23, 6:46 am, Christian Goudreau <[email protected]> wrote: > Yes they use annotations, but there's no enhancement process like in JDO, so > you can reuse your model without any problem. I use Twig for my projects > with GWT and It's just wonderful ! > > Twig-Persist is optimised for AppStore Datastore, so if there's any draw > back, the come directly from the limitation of the datastore. I used > Objectify before migrating to Twig, I don't really know wich one is better, > but Twig is simplier. > > I mean: why would anyone use anything else? > > The answer to this question is simple, because they don't know about > Objectify, Twig or SimpleDS yet. Or want to connect they're app to another > datastore than the one in AppEngine. > > Christian > > > > On Fri, Apr 23, 2010 at 7:42 AM, jbdhl <[email protected]> wrote: > > Interesting! But Twig-Persist and Objectify both uses their own > > annotations too. Doesn't that prevent me to re-use the objects on the > > client side in GWT? > > > Another thing: Twig-Persist seems to address all the short-comings of > > Objectify, JDO and SimpleDS. Doesn't Twig-Persist have any draw-backs? > > I mean: why would anyone use anything else? It seems that there are no > > real advantages with e.g. JDO? I'm confused. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google Web Toolkit" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<google-web-toolkit%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-web-toolkit?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
