Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
At present, we have a number of web services where when we send data to them, we send it as a string which is an XML block and the web service parses and does some work.
Similarly, when we need data from a web service, we are returning a string which is again an XML block which the client application parses.
Are there disadvantages in doing it this way. Also should we be returning types that get serialized to xml?
JD
If you send XML as a string and return it as a string, you may as well use REST.
The whole point of webservices is that the XML serialization and deserialization (marshalling/unmarshalling) is taken care of for you, so simply pass complex types around, or a Request object as input and return a Response object.
And you get strong typing without any effort.