SOAP provides the envelope for sending Web Services messages over the Internet/Internet. It
is part of the set of standards specified by the W3C. Those standards are an
alternative to the principles of
Representational State Transfer (REST) (new window).
The SOAP envelope contains two parts:
An optional header providing information on authentication, encoding of data, or how a recipient of a SOAP message should process the message.
The body that contains the message. These messages can be defined using the WSDL specification.
SOAP commonly uses HTTP, but other protocols such as Simple Mail Transfer Protocol (SMTP) may by used. SOAP can be used to exchange complete documents or to call a remote procedure.
NOTE: SOAP at one time stood for Simple Object Access Protocol. Starting with SOAP Version 1.2, the letters in the acronym have no particular meaning.
Interview: Pete Lacey on REST and Web Services InfoQ.com, Canada - 6 hours ago Pete Lacey is a well-known critic of the SOAP/WSDL-based approach to Web services, and a fierce advocate of the REST style. (See our previous coverage of ...
Web Applications Developer Seattle Post Intelligencer - 3 hours ago An understanding of "WEB 2.0" technologies (RSS, AJAX, Mashups, SOAP, Web Services and Web API's) as they apply to web environments 6. ...
JavaOne 2008: A Day One Report From the Sessions SYS-CON Media, NJ - 6 hours ago Almost all of their services are non-Web-Service (the Big Web Services as RESTful camp would call them) services. They chose not to introduce extra layers ...
Mule architect sees REST with Atom rising, UDDI fading SearchSOA - May 12, 2008 While SOAP and WSDL caught on, UDDI, the third leg of the Web services stool, has never enjoyed much popularity even as governance became more important to ...
Mocking Web Services InfoQ.com, Canada - May 10, 2008 Apache Synapse can be used to filter, transform, route, manipulate, and monitor SOAP, binary, XML, and plain text messages that can be delivered by HTTP, ...
Understanding Web Services: XML, WSDL, SOAP, and UDDI (Independent Technology Guides) by Eric Newcomer Average Customer Review: based on 25 reviews. Customer Review: This title is very good for understanding basic WS technologies. But is older for now and some informations are outdated. Reprint with updated information (espec. UDDIv3) would be good.
Building Web Services with Java: Making Sense of XML, SOAP, WSDL, and UDDI (2nd Edition) (Developer's Library) by Steve Graham, Doug Davis, Simeon Simeonov, Glen Daniels, Peter Brittenham, Yuichi Nakamura, Paul Fremantle, Dieter Koenig, Claudia Zentner Average Customer Review: based on 36 reviews. Customer Review: This book has helped me immensely in implementing some really intense production quality data interchange across systems using web services. This book will quickly help you understand the entire XML stack of technologies that you will need for Web Services. The authors have uniquely enabled the readers to develop an understanding of...
Perspectives on Web Services: Applying SOAP, WSDL and UDDI to Real-World Projects (Springer Professional Computing) by Olaf Zimmermann, Mark R. Tomlinson, Stefan Peuser Average Customer Review: based on 5 reviews. Customer Review: My primary reason for buying this book was the eye-catcher word "Real-World Projects" in the subtitle. I'm a professional developer/architect of enterprise size IT-projects and the fastest way for me to learn new things is by using examples. So in fact the "Development Perspective" chapter was the first chapter I've read and found it...
Web Services Platform Architecture: SOAP, WSDL, WS-Policy, WS-Addressing, WS-BPEL, WS-Reliable Messaging, and More by Sanjiva Weerawarana, Francisco Curbera, Frank Leymann, Tony Storey, Donald F. Ferguson Average Customer Review: based on 7 reviews. Customer Review: What do you get when you put a number of Web Services gurus from IBM in a room for a while? You'll get the "Web Services Platform Architecture" book. In short, all the authors that assisted in writing this book are Web services experts from IBM who have either wrote the specs or assisted in writing the Web services specs in question....