I am interested in the very same thing. So far my questions have left unanswered. http://groups.google.com/group/google-web-toolkit/browse_thread/thread/b86693200c8f3179
You can find similar thread here: http://groups.google.com/group/gwt-platform/browse_thread/thread/39bbc24842168f6a Based on my understanding, some of the challenges for doing REST with GWT are: 1- JSON<->POJO conversion (especially for complex objects, maps, polymorphic types) on the client side (since GWT ends up as JavaScript, and there is no Reflection support there) 2- Data Binding 3- URL handling etc there are a number of third-party open-source projects that provide libraries that one can put together to do REStul apps with GWT. However there is no unified framework, and no official solution/best practice from Google. I am afraid if you use the open-source tools, you might eventually get your app working (RESTful), but you have to deal with the risk of these tools not being around, or being experimental or buggy, also not being able to take advantage of many interesting features of GWT 2.1 and down the road, Google Team going in one direction, you might be left on your own with limited support. and the skills you learn might not be transferable in another team/ company recently with 2.1.1 Google team released AutoBean which seems to help with JSON/POJO handling however there are virtually no clear documentation and not even a basic hello world sample of those. I prefer REST over RPC/RequestFactory, because REST/JSON is universal/ service oriented rather than binary (in case of RPC) and data oriented in case of RF. RPC/RequestFactory somehow remind me of old days of Distributed Objects/CORBA/DCOM and I'm afraid sooner or later Google Team/Community might realize this. Lets say you want to host part of your app on Amazon EC2, and part of it on GAE. (GAE poses many restriction that one has to chose this approach), and lets say you want to use a mature serverside framework such as Spring for the back end. (to take advantage of enterprise integration features it offers : Spring Security etc) GWT RequestFactory, ties the client to server, they are decoupled through the use of Interfaces, but so was CORBA/DCOM. it might be de-coupled but not loosely coupled enough. the entire point behind SOA was LooseCoupling. but with GWT I have the feeling that we are going backwards instead of forward. GWT is rich and has many aspects. Ofcourse I am not talking about the Compiler/Widget Library/Model View Presenter, my comment was mainly the Client/Server Communication mechanism. -- 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.
