What about generating DAO classes ? http://code.google.com/p/audao/ The generated code calls GAE low-level datastore API directly without reflection.
Vaclav On Oct 11, 11:50 am, Maxim Veksler <ma...@vekslers.org> wrote: > Hi Didler, > > This is a bit off topic from the main discussion I was hoping to have on > this thread but still: Objectify is an over kill *for our needs*. It's > faster for us to simply wrap calls to low level DataStore in > LowLevelDataStore.java calls we make (which return an > Entity, List<Key>, Iterable<Entity> and co.) in a Repository.java that > transforms them into application POJO then use Objectify for this which we > will need to register the classes and pass through the Objectify > abstraction. > > Objectify, Twig itself are great libraries and we are using them in GUI apps > that are running on the app engine. > > Maxim. > > On Mon, Oct 11, 2010 at 10:01 AM, Didier Durand > <durand.did...@gmail.com>wrote: > > > Hi Maxim, > > > When you say Objectify is overkill,what do you mean ? Did you > > benchmark it ? > > > I switched ito it from JDO and I am pretty satisfied: slick and fast. > > What is bad about it from your perspective ? > > regards > > didier > > > On Oct 10, 11:28 pm, Maxim Veksler <ma...@vekslers.org> wrote: > > > Hello, > > > > The application we run is a backend online service and has no GUI. > > > We some how need to be able to upload new content / update existing > > > datastore entity records. > > > > The database model is relatively simple: 1 to many relationships on all > > of > > > the kinds. > > > > I would be happy to use learn about a library / some API configuration > > > option to expose an interface so that external code can do the CRUD > > logic. > > > Is there any support for this in GAE / other library that runs on GAE? > > > > If this plays any role in your suggestions: > > > We're super focused on response times so: We currently use "low level" > > data > > > store API. > > > I actually tried Objectify but found even it to be an over kill for our > > > needs. > > > I also deleted all the jars the were added by GAE eclipse plugin but are > > not > > > used by the code. > > > > Actually the list of jars used by the application consists of: > > > > ls war/WEB-INF/lib/ > > > appengine-api-1.0-sdk-1.3.7.jar appengine-jsr107cache-1.3.7.jar > > > jackson-core-asl-1.6.0.jar jsr107cache-1.1.jar > > > appengine-api-labs-1.3.7.jar EyeViewUtils-1.0.1-SNAPSHOT.jar > > > jackson-mapper-asl-1.6.0.jar log4j-1.2.16.jar > > > > Any recommendations / personal experience with this issue / pointers > > about > > > correct design of the interface / what technology to use and co. are > > highly > > > welcome and appreciated. > > > > Thank you, > > > Maxim. > > > -- > > 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<google-appengine-java%2bunsubscr...@googlegroups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-appengine-java?hl=en. -- 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.
