InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

WS-RM 1.1 Committee Draft Published

Posted by Stefan Tilkov on Aug 26, 2006

Sections
Enterprise Architecture
Topics
SOA ,
WS Standards
Tags
OASIS ,
WS-Reliable Messaging ,
WS-Reliability
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.
  • This article is part of a featured topic series on SOA
Public Review starting by Paul Fremantle Posted
Re: Public Review starting by Stefan Tilkov Posted
  1. Back to top

    Public Review starting

    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

    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 ;-)

Educational Content

Jesper Boeg on Priming Kanban

In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.