On 12 juil, 19:34, PhilBeaudoin <[email protected]> wrote: > Following an off-group discussion with Marius, he suggested that I > comment back on this thread regarding the fear of many gwt-platform > users and developers that the GWT MVP approach is too tightly linked > to SpringRoo and the idea that it can generate a lot of boilerplate > automatically. Do you think this apprehension is grounded, or that > GWT's MVP can lead to lean code even when written manually?
First, it's a stated goal that RequestFactory/ValueStore is usable "easily enough" without tooling such as Roo: https://wave.google.com/wave/waveref/googlewave.com/w+WU4iAICkI Key phrase: "this is definitely intended to be useful without Roo" That being said, when you have many model objects, coding the as-many Record interfaces and the @Service interfaces on the client-side is cumbersome. This is going to change a bit though: M1 required a ServerOperation enum for each @Service interface and a server-side Config, M2 removes this using reflection on the server-side (as the default implementation, because it's pluggable), and the goal is to remove even more ("The Property types are cumbersome and we plan to drop them"). We're starting prototyping, so it's OK to code those things by hand (and play by the current limitations: I'm coding a server-side object extending a model object just to add the findXxx, persist and remove methods), but if it proves necessary (or just worth it), we'll use generators, probably in the form of an annotation processor. (FWIW, we're using Morphia on the server-side to persist POJOs into MongoDB, which is quite similar what Objectify is for AppEngine AFAICT) Time will tell if RequestFactory fulfills its stated goal of being "easy enough" to be used without Roo, but it's promising and I guess only feedback from the community will help make it useful in as many contexts as possible (proof that Gogle is listening: the RequestFactoryServletHelper answers an early user request) -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. 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.
