The db story of GAE/J looks really sad: - the low level api is erm... too low level. - the 'official' datanucleus jdo/jpa apis seem abandoned. - there are some interesting third party efforts (objectify, twig, simpleds) but I don't really feel safe with third party solutions.
Given the fact that the db layer is central in typical web applications, I would expect that Google provides a convincing solution to this 'issue' ASAP. It's unbelievable that only a single developer is (was?) working on such a critical part or the GAE/J offering. regards, -g. PS: How about bringing the original datanucleus developers on team? On Nov 24, 11:56 am, Ian Marshall <[email protected]> wrote: > +1 on this one. DataNucleus is a core library for those of us using > JDO or JPA. > > I am fairly ruthless in avoiding third party plug-ins for my GAE/J app > in order to minimise the risk of improvements stopping permanently, > but I decided to use JDO so I have no choice but to depend on GAE's > use of DataNucleus. > > Max Ross of Google seems to have disappeared from view since the end > of August. He did (and hopefully still does) lots of datastore-related > work. > > On Nov 23, 2:48 pm, George Moschovitis <[email protected]> > wrote: > > > > > > > > > Are there any plans to resume work on datanucleus-appengine? > > > The progress on this lib seems to have stopped 6 months ago and there > > still a lot of related issues in the tracker: > > > update to the latest version of datanucleus, support for unowned > > relations, support for more jdo/jpa features, jpa docs and more... > > > is there a roadmap for this important library? > > > thanks, > > -g. -- 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.
