Yeah SOAP was all that about 5 - 7 years ago in the SOA world. However, I don't think there were ever really any services that I consumed via SOAP that really utilized SOAP so much that it had to be done with SOAP.
The protocol itself is in depth so it makes sense for complex services but not for simple services where REST is better. My question. is that WSDL endpoint that you can access or is this just straight up SOAP with no WSDL? If there is a WSDL you should be able to do what Frank is saying and create the stubs. Typically in java you can do by using the WSDL2Java tool. Another way is to write an interface where you consume the SOAP service and provide an endpoint to your android client to make calls to which could be as simple as an HTTP POST/GET api, which does all of the heavy SOAP lifting. Best of luck. Joe On Nov 2, 1:36 pm, Frank Weiss <[email protected]> wrote: > If you have to use it because the legacy server uses it, I would recommend > using a SOAP package to create the client stub source code and adapt that > code to Android. -- You received this message because you are subscribed to the Google Groups "Android Developers" 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/android-developers?hl=en
