If you have *only* WSDL + SOAP ...
1 view
Skip to first unread message
Joseph N. Hall
May 9, 2008, 6:40:50 PM5/9/08
to Google Web Toolkit
I have a server that speaks SOAP, period, but I'd like to investigate
using GWT as a client front end. The answer to "What about SOAP with
GWT?" usually comes up as "speak something else to the server" but I
have no control over the server, and don't want it - SOAP is the API.
So, what can be done? Have I missed something along the lines of "Oh,
by the way, we added SOAP support via xxyyzz."
using GWT as a client front end. The answer to "What about SOAP with
GWT?" usually comes up as "speak something else to the server" but I
have no control over the server, and don't want it - SOAP is the API.
So, what can be done? Have I missed something along the lines of "Oh,
by the way, we added SOAP support via xxyyzz."
Jason Essington
May 9, 2008, 7:03:04 PM5/9/08
to Google-We...@googlegroups.com
GWT provides XML support, so you could port an existing SOAP framwork,
or write your own. SOAP is actually fairly complicated if you try to
handle all of the edge cases, so a full implementation in GWT might be
difficult.
or write your own. SOAP is actually fairly complicated if you try to
handle all of the edge cases, so a full implementation in GWT might be
difficult.
I think that Mozilla used to have SOAP support built into the browser,
so maybe that is a common feature across the MOZ based browsers, but I
doubt that it exists in IE, Safari, and Opera.
-jason
Peter Blazejewicz
May 12, 2008, 5:54:18 PM5/12/08
to Google Web Toolkit
hi Joseph,
there are plenty existing native javascript libraries for soap on
client, just google for "javasript soap",
There are event articles on that:
http://www.ibm.com/developerworks/webservices/library/ws-wsajax/
in GWT (and javascript) we can talk to every soap api bypassing same-
domain-policy with smart (and hacky) use of google.feeds with raw xml
format,
You could either go GWT XML module way (adding your cusotm parsing and
building bodies/envs). However you can get several stoppers during
implementation: IE does not support namespaces well or at all
depending on version, see GWT api: there is no
getElementsByTagNameNS(namescape, name) for that reason.
I would rather search for solid javascirpt soap library and bind it to
GWT with JSNI (so you won't to work with xml handling natively)
regards,
Peter
there are plenty existing native javascript libraries for soap on
client, just google for "javasript soap",
There are event articles on that:
http://www.ibm.com/developerworks/webservices/library/ws-wsajax/
in GWT (and javascript) we can talk to every soap api bypassing same-
domain-policy with smart (and hacky) use of google.feeds with raw xml
format,
You could either go GWT XML module way (adding your cusotm parsing and
building bodies/envs). However you can get several stoppers during
implementation: IE does not support namespaces well or at all
depending on version, see GWT api: there is no
getElementsByTagNameNS(namescape, name) for that reason.
I would rather search for solid javascirpt soap library and bind it to
GWT with JSNI (so you won't to work with xml handling natively)
regards,
Peter
George Georgovassilis
May 14, 2008, 1:10:46 AM5/14/08
to Google Web Toolkit
If you have absolutely no control over the server then you can't do
GWT either because of the same origin policy: you won't be able to
communicate with the SOAP services if they reside on a different
domain than the static resources serving the GWT code...
GWT either because of the same origin policy: you won't be able to
communicate with the SOAP services if they reside on a different
domain than the static resources serving the GWT code...
Reply all
Reply to author
Forward
0 new messages