GWT roadmap: easier use of REST?
Hi, A lot of web APIs use REST nowadays. GWT seems really well suited to build mashups/UIs on top of REST web services. However, it's not that easy to work with REST from GWT (see also http://groups.google.com/group/google-web-toolkit/browse_thread/thread/71f2d5599ee2593f/41ef729a5d1cfe8d?lnk=gst&q=rest#41ef729a5d1cfe8d ) There are two projects tackling this: * Restlet http://blog.noelios.com/2008/07/25/restlet-ported-to-gwt/ * SmartGWT's http://www.smartclient.com/smartgwt/javadoc/com/smartgwt/client/docs/ClientDataIntegration.html (it provides DataSources, then makes it easy to have REST DataSources, both read/write) Are there any plans to improve out-of-the-box GWT to work with REST, so no additional libraries are needed? Is there a wish list to submit this request? Thanks -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@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.
Re: GWT roadmap: easier use of REST?
Hi Marius, I guess directly supporting RESTful/Soap does not make much sense because of SOP and other security topics. At this time I would recommend always to use GWT-RPC to communicate. >From the server SOP does not apply and you can access any webservice you like. Stefan Bachert http://gwtworld.de On 9 Jul., 11:39, "marius.andreiana" wrote: > Hi, > > A lot of web APIs use REST nowadays. GWT seems really well suited to > build mashups/UIs on top of REST web services. > > However, it's not that easy to work with REST from GWT (see > alsohttp://groups.google.com/group/google-web-toolkit/browse_thread/threa... > ) > > There are two projects tackling this: > * Restlethttp://blog.noelios.com/2008/07/25/restlet-ported-to-gwt/ > * > SmartGWT'shttp://www.smartclient.com/smartgwt/javadoc/com/smartgwt/client/docs/... > (it provides DataSources, then makes it easy to have REST DataSources, > both read/write) > > Are there any plans to improve out-of-the-box GWT to work with REST, > so no additional libraries are needed? Is there a wish list to submit > this request? > > Thanks -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@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.
Re: GWT roadmap: easier use of REST?
On Jul 9, 7:02 am, Stefan Bachert wrote: > I guess directly supporting RESTful/Soap does not make much sense > because of SOP and other security topics. With browsers becoming more aware and supporting sources from multiple sources, SOP is not so much an issue. > At this time I would recommend always to use GWT-RPC to communicate. > From the server SOP does not apply and you can access any webservice > you like. That is a sad state of affairs and ties the client to a GWT-RPC speaking backend. I know many people are impressed by the flexibility and power of GWT as a client side technology (especially on html5 enabled mobile devices!!!), but would like to use alternative tools on the server (eg: rails). Proper REST support would really ease the way for developers to create cleanly separated clients using GWT and backends using whatever RESTful tools they want. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@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.
Re: GWT roadmap: easier use of REST?
> With browsers becoming more aware and supporting sources from multiple > sources, SOP is not so much an issue. first of all SOP is a browser topic not an GWT. I don't think that browsers will give up security. > That is a sad state of affairs and ties the client to a GWT-RPC > speaking backend. It is probably the most secure approach. You can switch to JSON(P) if security is not important. > > I know many people are impressed by the flexibility and power of GWT > as a client side technology (especially on html5 enabled mobile > devices!!!), but would like to use alternative tools on the server > (eg: rails). Proper REST support would really ease the way for > developers to create cleanly separated clients using GWT and backends > using whatever RESTful tools they want. What is the problem to call them from GWT-serverside ? (By the way, Spring Roo may become a substitute for rails when fully supporting GWT) To mashup to any service from browser looks only attractive at the first glance. It would be a security disaster. No browser vendor will allow this. Stefan Bachert http://gwtworld.de -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@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.
Re: GWT roadmap: easier use of REST?
On 9 juil, 17:18, ivar vasara wrote: > On Jul 9, 7:02 am, Stefan Bachert wrote: > > > I guess directly supporting RESTful/Soap does not make much sense > > because of SOP and other security topics. > > With browsers becoming more aware and supporting sources from multiple > sources, SOP is not so much an issue. > > > At this time I would recommend always to use GWT-RPC to communicate. > > From the server SOP does not apply and you can access any webservice > > you like. > > That is a sad state of affairs and ties the client to a GWT-RPC > speaking backend. > > I know many people are impressed by the flexibility and power of GWT > as a client side technology (especially on html5 enabled mobile > devices!!!), but would like to use alternative tools on the server > (eg: rails). Proper REST support would really ease the way for > developers to create cleanly separated clients using GWT and backends > using whatever RESTful tools they want. What do you call "proper REST support"? Which kind of API would you like to see added to GWT? I'm curious. As REST is strongly tied to media types, you'd have you register media type "processors", but that's not really different from what you can already do today with RequestBuilder (without the need for GWT generators, contrary to GWT- RPC, unless you'd like something like XStream- or Jackson-like serialization on the client-side), so I wonder. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@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.
Re: GWT roadmap: easier use of REST?
GWT has a bug that prevents it from being use with Restlet. The Restlet framework has direct support for both Appengine, as a service provider, and GWT as a client. However, a bug added to GWT since 1.7 makes it impossible to use GWT with a restlet server if you want to use XML representations. It may may work fine with JSON. Here is the reference to the issue tracker; http://code.google.com/p/google-web-toolkit/issues/detail?id=4267. If you want GWT to be fully compatible with Restlet (which is an excellent package), please go and star this issue. Ed On Jul 9, 2:39 am, "marius.andreiana" wrote: > Hi, > > A lot of web APIs use REST nowadays. GWT seems really well suited to > build mashups/UIs on top of REST web services. > > However, it's not that easy to work with REST from GWT (see > alsohttp://groups.google.com/group/google-web-toolkit/browse_thread/threa... > ) > > There are two projects tackling this: > * Restlethttp://blog.noelios.com/2008/07/25/restlet-ported-to-gwt/ > * > SmartGWT'shttp://www.smartclient.com/smartgwt/javadoc/com/smartgwt/client/docs/... > (it provides DataSources, then makes it easy to have REST DataSources, > both read/write) > > Are there any plans to improve out-of-the-box GWT to work with REST, > so no additional libraries are needed? Is there a wish list to submit > this request? > > Thanks -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@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.
