Hi Graeme, regarding point 2) I discovered that it works if you have a @Id Long id but NOT if you use a datastore Key (which you have to use (!) when using owned OneToMany relations). The Datastore Key gives the following error with the scaffolded controllers/views:
Error 500: Error processing GroovyPageView: Error executing tag <g:form>: org.codehaus.groovy.grails.web.pages.exceptions.GroovyPagesException: Error evaluating expression [com.google.appengine.api.datastore.Key.list()] on line [33]: groovy.lang.MissingMethodException: No signature of method: static com.google.appengine.api.datastore.Key.list() is applicable for argument types: () values: [] I just tried to reproduce this with a minimal project in order to file a bug. But unfortunately, due to http://jira.codehaus.org/browse/GRAILSPLUGINS-1295 I now never get past the NullPointerException any more. ... and that after spending hours with the fact that the libraries of grails get mixed and conflict with the user libraries in grails-app/ lib, the fact that the stage directory is not cleared (together a deadly combination :-( ), with the "classpath gets too long problem under XP/Cygwin", bug GRAILSPLUGINS-1257, bug GRAILSPLUGINS-1168 etc. Altogether, a rather unpleasant experience after my initial enthusiasm with grails. ... No offence! But the app-engine/gorm-jpa stuff needs significant work. Maybe, I can help in a few weeks during my holidays (I am afraid my groovy/grails knowledge is not sufficient yet). Keep up the good work. Regards, Chris On 22 Sep., 09:21, "[email protected]" <[email protected]> wrote: > Hi, > > To address your points: > > 1) Yes you have to use app-engine run. If the Google team are able to > show how we can programatically start the Jetty service and have > access to the full Jetty API directly then we can get run-app > working. > 2) Scaffolding templates work for me, but I understand Keys are > preferable > 3) The PMF is configured by Spring and hence is injectable into any > service, domain class or controller. The same is true of the EMF if > you're using JPA > > Regards, > > On Aug 14, 12:16 am, "Jason (Google)" <[email protected]> wrote: > > > Thanks for the note, Tom. I just updated the wiki page with this info. > > - Jason > > > On Wed, Aug 12, 2009 at 9:54 AM, Tom Ball <[email protected]> wrote: > > > In the Will it play in App > > > Engine<http://groups.google.com/group/google-appengine-java/web/will-it-play...>doc, > > > Grails 1.1.1 is listed as compatible with its app-engine plugin. > > > That's true only to a certain extent, but really basic support is broken: > > > . You have to use the "grails app-engine run" command instead of "grails > > > run-app". This blocks the use of plug-ins that extend run-app, which > > > breaks > > > Grails IDE support for project execution and debugging. > > > > . The GWT plugin can't co-exist with the app-engine plugin, due to the > > > above problem. > > > > . The scaffolding files generate domains, controllers, and views that are > > > broken on delivery. This is mostly due to domain classes created with > > > Long > > > ids instead of Keys. Looking at the one example, it's obvious that none > > > of > > > the controllers or views were based on scaffolding code. > > > > . The PMF is hidden away, making it impossible (as far as I can tell) for > > > services to access domain classes. > > > > I vote that the "compatible" label for Grails on App Engine be changed to > > > "semi-compatible" until these issues are addressed somehow. > > > > Tom > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
