This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
While you don't say what "secure" should involve in your case, this is generally the domain of the WS-Security standard (which all major SOAP stacks support). Read the documentation of whichever stack you're using to learn how to apply it. If you're not using SOAP, tell us how the WS is implemented.
Thank you very much for this link. The content is awesome.
That is what I was looking for to understand more.
Thanks for your reply too.
I guess it was implemented using SOAP.
But I am a bit confused here, did you mean we could implement it using REST too?
I don't understand the difference though. I got to dig deep.
Wheather it's SOAP or REST the internal implemenation I think is XML over HTTP (not using SMTP/JMS for sure) and which is what SOAP is all about (right?).
Please correct me.
Joined: Mar 22, 2005
SOAP is an XML dialect, whereas XML is not generally used with REST (definitely not as part of the request), so the odds are you're working with a SOAP WS. The WebServicesFaq has some good material about both SOAP and REST.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com