I agree the documentation isn't fabulous for JPA, in that a vast majority of it focuses on the JDO implementation and you end up having to work out which bits of DataNucleus documentation should be used and is relevant for GAE. However, to give the team a bit of credit the restrictions you are talking about are clearly documented at http://code.google.com/appengine/docs/java/datastore/transactions.html.
Having been through the pain with trying a JPA-based implementation and reading through these message groups, it is quite clear that JDO and JPA are just a very poor fit for the underlying datastore - using the low-level API, or one of the open-source libraries such as Objectify, Twig or Slim3 is probably a safer bet. On Oct 25, 4:01 am, Shawn Brown <big.coffee.lo...@gmail.com> wrote: > > I'm just here because i feel i need to rant a little. I came here expecting > > way too much. > > Been there with JDO -- the docs are not adequate. > > I don't know your exact requirements but I suspect you'll find many on > this list who found objectify to be the "simplest convenient interface > to the Google App Engine > datastore".http://code.google.com/p/objectify-appengine/ > > Shawn -- 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-j...@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.
