WS-RM 1.1 Committee Draft Published
Posted by
Stefan Tilkov
on
Aug 26, 2006 02:56 PM
- SOA
- Topics
- WS Standards
- Tags
- WS-Reliability,
- WS-Reliable Messaging,
- OASIS
When two parties want to communicate reliably using SOAP messaging, the most common option is to select a message queueing system, typically JMS-based. While this provides some portability, is does not create interoperability — which means that reliable communication is restricted to those communication partners who are able and willing to connect to the same middleware.
WS-ReliableMessaging 1.1, which
has just become an OASIS committe draft, provides an interoperable solution to this problem. It achieves this by implementing the necessary protocol on top of SOAP, which means that even an unreliable communication protocol such as HTTP can be used as the basis for reliable communication. One of the most important scenarios for this is B2B interaction, i.e. communication between distinct companies.
The committee draft status is significant because it marks the end of the most frequently cited Web services standards battle. OASIS has already ratified a standard addressing the same problem,
WS-Reliability, originally created by Sun, Fujitsu, Novell, Oracle and Sonic. Proving expectations expressed by many analysts and industry experts correct, it never gained wide-spread adoption because industry heavyweights such Microsoft and IBM, together with BEA and TIBCO, pursued their similar, but distinct specification:
WS-ReliableMessaging. Both specifications were originally published in early 2003; WS-Reliability became a standard in November 2004.
WS-ReliableMessaging, which had been updated twice (in 2004 and 2005) was
submitted to OASIS in April 2005. The committee draft specification of WS-ReliableMessaging 1.1 has been created with support from many of the companies who were involved in WS-Reliability and the original WS-ReliableMessaging spec. WS-ReliableMessaging is based on
WS-Addressing (itself now a W3C recommendation); the accompanying
Web Services Reliable Messaging Policy Assertion v1.1, which is based on WS-Policy (also recently submitted to W3C), defines how to express reliability-related messaging capabilities and needs.
2 comments
Reply