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 pretty painless creating small-scale, simple apps. For large-scale projects, IMHO, *far *too much scaffolding code just to move POJOs back and forth. 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. http://code.google.com/p/spring4gwt/ -- this may be of interest if you're Spring-based. May be of interest even if not. :-) If you're dealing with one application, particularly a small one, I'd go with RequestFactory. I have to deal with 6 rather large applications, with 5 different databases. Even though I don't use any two at the same time (JTA), I'm finding neither Guice Persist nor RequestFactory really fits well and failover is still problematic. As a result, I find it best to simply push POJO events back and forth between the UI and the Server. SOC for me. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/AxZRy4vSZTgJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
