That's a little misleading in that RequestFactory useage requires a
considerable amount of scaffolding code.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
After digging into both, I'm moving towards GWTEventservice:
http://code.google.com/p/gwteventservice/.
RequestFactory seems best fitted to CRUD operations on specific model
entities and does offer much under the covers in supporting those
operations. Combined with UIBinder and Editors, it's
It was also a bit of a pain getting integrated with Spring and Guice,
though I'm sure that pain will be alleviated as the releases progress.
I don't know about Spring, but integrating RF and Guice is not that hard and
works very well
On Fri, Aug 26, 2011 at 12:40 PM, Brian Lough bklo...@gmail.com
There is almost no difference in configuration between GWT RPC and GWT
Request Factory. The only difference is web.xml needs to declare
RequestFactoryServlet instead of RemoteServiceServlet.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit
They both seem to scale. The main difference is when RPC is used the server
works with POJOs that need to be translatable and that need to be mapped to
database records by hand or by some tools. Request Factory works with
objects that do not need to be translatable: the may come directly from
Hi
How to integrate gwt request factory with tomcat
Thanks
Srinivasan Raghavan
On Tue, Aug 23, 2011 at 9:46 PM, Y2i yur...@gmail.com wrote:
They both seem to scale. The main difference is when RPC is used the server
works with POJOs that need to be translatable and that need to be mapped to
