InfoQ

News

WS-RM 1.1 Committee Draft Published

Posted by Stefan Tilkov on Aug 26, 2006 02:56 PM

Community
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

Public Review starting by Paul Fremantle Posted Aug 27, 2006 11:11 AM
Re: Public Review starting by Stefan Tilkov Posted Aug 27, 2006 1:31 PM
  1. Back to top

    Public Review starting

    Aug 27, 2006 11:11 AM by Paul Fremantle

    Stefan Good article. I just want to clear up one point. This is slightly more important than just an OASIS Committee Draft. Without going into the whole OASIS process, this is our first public review, and the main chance for interested parties to comment. Based on the feedback we aim to try to get WSRM 1.1 standardised by around the end of the year. Not only is this an opportunity to provide feedback, this is also a major "stake in the ground" for the technical committee. We have resolved all the major issues we raised as a group, and we believe the spec is in good shape. Paul Fremantle Co-chair - OASIS Web Service Reliable exchange TC

  2. Back to top

    Re: Public Review starting

    Aug 27, 2006 1:31 PM by Stefan Tilkov

    Thanks for your comment, Paul. If the news item did not communicate the importance, it was unintentional -- I'm very much aware of the importance for the WS-* community. Congrats for getting it out the door ;-)

Exclusive Content

Rationalizing the Presentation Tier

Thin client paradigm characterized by web applications is a kludge that needs to be repudiated. Old compromises are no longer needed and it's time to move the presentation tier to where it belongs.

Agile Project Management: Lessons Learned at Google

In this presentation filmed during QCon 2007, Jeff Sutherland, the creator of Scrum, talks about his visit at Google to do an analysis of Google's first implementation of Scrum.

AtomServer – The Power of Publishing for Data Distribution

In this article, Bryon Jacob and Chris Berry introduce AtomServer, their implementation of a full-fledged Atom Store based on Apache Abdera, which is now available as open source.

An Introduction to Virtualization

It is easy to think that virtualization applies only to servers. In reality the recent resurgence of the concept is also being applied to networking, storage, and application infrastructure.

REST Anti-Patterns

In this article, Stefan Tilkov explains some of the most common anti-patterns found in applications that claim to follow a "RESTful" design and suggests ways to avoid them.

Choosing between Routing and Orchestration in an ESB

In this article, Adrien Louis and Marc Dutoo discuss the differences and relative merits of using orchestration vs. routing in a typical ESB setup, and discuss various implementation options.

Enterprise Batch Processing with Spring

Wayne Lund discusses batch processing, Spring Batch objectives and features, scenarios for usage, Spring Batch architecture, scaling, example code, failures and retrying, and the future roadmap.

User Story Estimation Techniques

Developer Jay Fields draws on his experiences as a ThoughtWorks consultant to describe effective user story estimation techniques.