I couldn't agree more with Jeff. JDO/JPA on GAE is pants for any real project.
I am part of a 4 person development team that recently completed a fairly hefty 6 month GAE project built using GAE, GWT and Guice. We used JDO/Datanucleus for the persistence technology which caused significant problems across the project. As well as the issues that Jeff points out, simple things like IDE integration (predominantly Eclipse) with Datanucleus never seemed to work very well. Getting transaction demarcation to work with how the store 'actually' works is also practically impossible. We burnt a lot of days getting around a mass of silly little issues for no real benefit. To be clear, in standard relational environments we'll use Hibernate (et al) almost exclusively as an ORM, but, in my view, trying to use JDO/JPA on GAE is at this point in time a frivolous exercise that ultimately will heavily limit what you can do on the platform (not discounting the great work done be those that did port the standard over). It also lures you into this familiar relational way of looking at persistence problems which really does not, in any way, translate to how the datastore actually works. I'd be very interested to know how Google's internal projects work with the store -- as presumably, it's going to be a fairly similar interface -- but, if we were starting from scratch, I'd lobby very hard for using the low-level API on its lonesome (it's already a pretty clean service). On Apr 5, 6:22 pm, SkYlEsS <shou...@gmail.com> wrote: > Thanks you so much for all this responses everybody ! -- 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.
