Since you're a student, and if you have the time, I'd recommend learning JDO for the following reasons: 1. You already know JPA. Might as well learn something new. :) 2. JDO, imo, fits the GAE datastore much better (I think there are quite a few discussions around here as to why).
Enjoy! On Mar 6, 8:28 am, itsnotvalid <itsnotva...@gmail.com> wrote: > Just in cast I want to make use of some existing Java APIs for messing > with DataStore, which may be the low-level API would work the best. > > I just wonder, as I am still a college student, one of my lecturer > told me that "we should use JPA (2.0) now as JDO is not the preferred > way for persisting data in JavaEE anymore." > > I just wonder, however, for the case with App Engine (which now most > of my assignments are implemented using JPA 2.0 with EclipseLink, > however,) is it best to use JPA or should I follow most tutorials and > use JDO instead? > > In view of the implementation of both APIs in App Engine, which one is > more robust, or which would is better in terms of performance? > > Hope to see Google staff to answer this newbie question. > > Thanks. > > Alan(@itsnotvalid) -- 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.
