Hi Joseph,
I don't know much about spring4gwt other than that the GWT-SL predates it by a while. After Robert Hanson and I released the SL in 2005 (or 2006, I forgot - at the time a SF project called "GWT Widget Library") it continuously evolved covering many corner cases such as exception translation. We also cooperated closely with the gilead (now defunc, I think) project that allowed transparent serialization of hibernate objects. The main idea is that the SL does not require that you extend any class; it rather works on an interface basis constructing proxies in run time that translate the GWT RPC protocol to method invocations on your POJO services. I personally use the SL for my own projects, so I've been keeping it up to date. Other than that, I see no reason to use the SL over anything else you feel comfortable with. After all, the best tools are the ones you know best :-)
On Thursday, 11 September 2014 19:50:24 UTC+3, Joseph Lust wrote:
-- I don't know much about spring4gwt other than that the GWT-SL predates it by a while. After Robert Hanson and I released the SL in 2005 (or 2006, I forgot - at the time a SF project called "GWT Widget Library") it continuously evolved covering many corner cases such as exception translation. We also cooperated closely with the gilead (now defunc, I think) project that allowed transparent serialization of hibernate objects. The main idea is that the SL does not require that you extend any class; it rather works on an interface basis constructing proxies in run time that translate the GWT RPC protocol to method invocations on your POJO services. I personally use the SL for my own projects, so I've been keeping it up to date. Other than that, I see no reason to use the SL over anything else you feel comfortable with. After all, the best tools are the ones you know best :-)
On Thursday, 11 September 2014 19:50:24 UTC+3, Joseph Lust wrote:
Thanks for your efforts. Clearly you've been working on this for some time.I'm curious what this framework does beyond the existing Spring annotation driven integration with RPC. Using SpringGwtRemoteServiceServlet , all the mapping of (annotated) service beans to paths can be done with Spring alone using @RemoteServiceRelativePath and extending RemoteService. In your loads of great documentation I see the ability to have XML files full of URL endpoint to bean mappings, which is more Springy. However, what else can you do here that generic Spring/GWT cannot? Thanks.Joe
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment