Comment by [email protected]:
I've made a somewhat-similar project (same goals, in a way, much different
route) - which is here:
http://code.google.com/p/alcina/
My comparison of the two (alcina to the gwt2.1/mvc framework)
-http://code.google.com/p/alcina/wiki/ComparisonWithGwt2_1Sync - is based
on gwt2.1 as it was in late June 2010, but still seems mostly valid.
The Alcina project is a lot closer to Google Wave (but with transforms of a
domain (JPA) object graph, not a wave) in many senses - and deals with a
few things that don't seem to be targetted by gwt2.1mvc, but perhaps would
be good if they were:
- non-blocking ("optimistic UI") client changes to the JPA graph
- out-of-order requests arriving at the server (only necessary if you're
non-blocking, sure)
- dealing with the client JPA graph being a sub-graph of that of the server
(essentially, dealing with EntityManager.merge() being basically broken)
Sorry this is so late - I tried emailing some of the GWT team in June but
got no response...best of luck, Nick
For more information:
http://code.google.com/p/google-web-toolkit/wiki/RequestFactoryPlusPaths
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
