I am encouraged by the contributions from Ikai and Max. I forgot to mention in my earlier post one reason I elected to use JDO as my interface to the datastore: to maintain the capability to port my application to another hosting service without too much work.
That being said, I have no intention currently of porting away from GAE/J. Despite various problems, I think that this is an excellent offering which improves continuously. A big thank you to everyone who is responsible! On Dec 5, 8:41 am, George Moschovitis <[email protected]> wrote: > On Dec 4, 6:56 am, John Howe <[email protected]> wrote: > > > Is that another "wave" I see on the horizon ... > > the news on the cloud-portability front are disappointing too: > > https://jira.springsource.org/browse/ROO-1797 > > Remove support for DataNucleus 1.x and Google App Engine > > Since none of Roo's sample apps can deploy to the app engine and given > there are a lot of hacks in the Roo code to allow even the simplest of > apps to run in the app engine, this task is to remove all the code > that supports the app engine until full SQL support is available. This > also has the added benefit of being able to drop support for JPA 1.0 > with the removal of DataNuclueus 1.x > > maybe another reason to update datanuclues-appengine to datanucleus > 2.x ? > > -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.
