Hi, You should also consider 3rd party packages like Objectify who works at an intermediate level of abstraction.
The low-level api forces you to handle everything by yourself: the Entity, its Properties, etc... In JPA, JDO: you work much higher in abstraction: you define a Java class as an Entity and then its properties become DS properties as you annotate them. As said: the big difference is abstraction level and resulting guidance for JDO or flexibility for low-level: with low-level, you can do much more things but you have to program much more carefully and now what you do. With JDO/JPA, you get more comfort as you are guided by the pojo structure. Also, JDO/JPA aligns you with Java (inheritance, compiler checks for types, etc...). I would really advise to start somewhere in the middle with a 3rd party package as they are recommended now by Google more than JDO/JPA and learn by using it at its own middle abstraction layer. When you understand better, you will see if you really want / need to go up or down in abstraction or stay where you are. regards didier On Apr 1, 1:50 pm, SkYlEsS <[email protected]> wrote: > I have a question : > > What are the differences between JPA/JDO and low level API (and > Objectify) in practice ? I read everywhere the low level API provides > more flexibility, but there are never samples code or evidences to > demonstrate it. So I'm wondering in which cases exactly, the low level > API is useful ? > > Thanks in advance -- 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 [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-appengine-java?hl=en.
