Out of curiosity, why would you need Spring at the server if you have a GWT
client?
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
For data access, Objectify of course.
We are using GWT for our rich client. It is really nice to be able to
share code between the client and backend.
Server side, we are using Spring. At first, we thought we would have
to switch to Guice to reduce our start times. But if you are careful
not to
My suggestion:
For datastore access use Objectify:
http://code.google.com/p/objectify-appengine/
For your MVC framework go with AJAX/Javascript/HTML5 and use Backbone.js:
http://documentcloud.github.com/backbone/
We've used Tapestry5 on App Engine before but without lazy loading and
serious
Thanks for pointing me to backbone.js. I am also looking at
knockout.js as well.
On Nov 20, 12:00 pm, Chris ritterch...@gmail.com wrote:
My suggestion:
For datastore access use
Objectify:http://code.google.com/p/objectify-appengine/
For your MVC framework go with AJAX/Javascript/HTML5 and
Jeff,
Thanks for your input. I looking into objectify for datastore access
in my app.
On Nov 20, 12:12 pm, Jeff Schnitzer j...@infohazard.org wrote:
My favored stack right now:
Objectify (I'm the lead developer, so this one was easy)
Resteasy + Htmleasy + Guice, tightly integrated
Cambridge
GWT !
no one mentioned GWT : (
On Nov 20, 4:54 pm, sppl spol...@gmail.com wrote:
I am starting off with a new project using app engine java. I am trying to
decide what mvc framework to use. I went through previous messages posted
by group members and found this
