I was going through the same thing. I ended up going back and rewatching the Ray Ryan architecture videos from 2009 and 2010 again, but this time drawing down all the diagrams, but combining them all. Then after having a big block diagram of the gwt framework and going the javadoc for the classes it just clicked into place. What I had problems with in the original readings of the docs, was that the overall big picture was really understated and somewhat confused by all the optional things. And an intended way(s) to use it combined with spring roo would help. That may be another piece of the puzzle for you. This framework depends a bit on spring roo to generate all the boilerplate code.
My way of using it has been to create a gwt project with the gpe. Then add spring roo to that project. Use Roo to create all the data enties, and request factories. At this point I'm guessing because here is where I am - let Roo add in the client side mvp and simple uibinder display areas into it's special generated folder/packagePath. Copy the display areas into my own and modify them the way I want and set up the places. Then add in backend logic. -- 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/-/WFp3ckpWRmpaX2dK. 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.
