On Friday, September 23, 2011 1:48:18 PM UTC-4, Thomas Broyer wrote: > > Did almost the same, but as a Maven plugin that scans the classpath for > classes extending a few base classes. > The only thing I regret: it's part of the build process, so proxies are > recreated each time, and therefore cannot be tweaked; which means that if > something needs to be tweaked, it has to be done at the code generator > level. > In retrospect, I'd rather have a "one shot" process: generate source code > so you can tweak it; and when you change your domain model, either you > update the proxies by hand, or you re-generate them. And because the > sources would be checked in SVN/Git/whatever, you could easily merge/ignore > the changes you made that the generator would have "cancelled". In other > words, similar to what the GPE can do in RequestFactory/AppEngine projects. >
Thomas -- You can have the best of both worlds by using the "generation gap" pattern. This is a technique we used very successfully in the Flex world via the GraniteDS GAS3 code generator. The idea is that you always generate the base classes on every build, but you also generate the concrete classes once. What is key is that the next level base inherits from the previous level concrete!! Thus your manual tweaks are persisted and you still get regeneration on every build...it was pure awesome! -- 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/-/JBw7w2ueuagJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
