views:

65

answers:

1

Hi, I currently have a Grails application I'm evaluating to port to Google App Engine and I'd like to know experiences regarding:

  1. Acegi security: the application relies on this library to enforce the security (update: just learned that it's based on hibernate so can't be ported; any recommended replacements?).
  2. Use of JPA or JDO instead of the hibernate plugin (I'll have to migrate the Domain classes); which one is better ?
  3. I have a growing number of pre-generated pdf files I keep uploading; is there any foreseeable problem with this?

Thanks in advance.

+2  A: 

This isn't the answer you want, I'm sure, but I spent some time exploring Grails on GAE and finally came to the conclusion that it's not a good fit. By the time you give up (or work around) the native Domain capabilities, forego many of the plugins, and deal with the host of other minor incompatibilities, you've essentially wiped out most of the productivity advantage of Grails. I'd consider a standard J2EE, a compatible framework, or possibly a GWT based app for GAE. If you want to stick with Grails, I'd host it on AWS or a dedicated J2EE hosting provider.

That said, I hope the integration eventually works cleanly because GAE is a pretty cool engine/model.

ecodan
Thanks for your reply. Actually it looks like CloudFoundry fits more adequately with Grail's philosophy - if it only supported Postgres I could port the app with no effort.
xain