Blake McBride <blake1024@...> writes: > > > Greetings, > > I ran through the same issues. Spent quite a bit of time banging my head against the wall. (Still am!!) I sense a lot of GWT stuff is simple to those who already know HTML/JavaScript/CSS/JSP/etc.. They understand what is going on underneath, what the limitations are, and what common workarounds are. For those of us non-experts in the above technologies, GWT is very difficult. It seems to be filled with arbitrary limitations and arbitrary mechanisms. It is sad in a way because I believe GWT was meant to hide all that stuff. In spite of all these frustrations however, I have found GWT to be the best thing out there. HTML is the worst environment I've ever seen for writing interactive applications by far! > > Naturally, GWT includes a communications mechanism that works and is sufficient if you write the front-end and backend in GWT. There is no need for trying to use another mechanism - you'd be adding a lot of unnecessary work. On the other hand, if you already have an existing back-end and you are trying to link it up with a GWT front-end you need something else like SOAP. I spent a huge amount of time trying all sorts of ways to get this working with little success for a long time until I finally settled on something that worked well. What I did was use GWT to create the front-end and backend so that the two sides were communicating in native GWT. I then had the GWT backend create a socket connection with the real backend and communicate with it. I created all of the code to very easily form the socket connection and have the ability to bi-directionally communicate via named methods and arbitrary structured data. This can all be done without adding new classes for each communication (to specify the arguments). Another beauty of this is that the real server and the GWT server can be operating on different machines, different URL's, different ports, etc.. > > I offered the code to the GWT community before but there was no interest. I haven't spent the time to package up the code due to the lack of interest but if you want it I'd be happy to package it up and give it to you. Let me know. > > Thanks, and good luck. > > Blake McBride > > > On Thu, Jul 26, 2012 at 6:03 AM, Nitheesh Chandran <nitheesh- [email protected]> wrote:Okay thanks for the information. Do you have experience of writing a soap client on the GWT server ? or else can i get any links regarding that ?Or do we have any alternatives that can be used instead of SOAP ? > On Thursday, July 26, 2012 1:59:28 AM UTC+5:30, Rob Whiteside wrote:You are right that GWT does NOT have built in support for making SOAP calls. GWT (like all javascript that runs in the browser) is subject to Same-Origin-Policy rules. So you couldn't call any remote soap service anyway. You can to do GWT- RPC to get to your server, then write a soap client on the server that sorta "proxies" the calls to the soap webservice. > > > --RobOn Tuesday, July 24, 2012 10:54:52 PM UTC-7, Nitheesh Chandran wrote: HI, > Can we use GWT and SOAP ? i read from some documents that GWT does not have a built in support for SOAP and another document says it can be used in server side of GWT. it is a little bit confusing. Can anyone give me a clarification on this. Also i read SMART GWT has built in support for SOAP webservices. But i am looking for GWT AND SOAP. Is that possible ? Thanks Nitheesh > > > > > >
-- 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.
