In other words this requires some high level hacking just to bring Data form A to B. I miss the simplicity in all this. GWT is becoming to over engineered imho.
2011/9/23 Thomas Broyer <[email protected]> > 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. > > -- > 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/-/k2On8kxH2H4J. > > 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. > -- GWT API for non Java based platforms http://code.google.com/p/gwt4air/ http://www.gwt4air.appspot.com/ -- 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.
