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-TX as an OASIS standard

Posted by Mark Little on Apr 18, 2007

Sections
Architecture & Design,
Enterprise Architecture
Topics
Web Services ,
Transactions Processing ,
SOA
Tags
WS-AtomicTransactions ,
Web services ,
WS-TX ,
WS-Coordination ,
WS-BusinessActivity
OASIS has just approved the output of the WS-TX technical committee as a standard. This means that WS-Coordination 1.1, WS-AtomicTransaction 1.1 and WS-BusinessActivity 1.1 can now join the ranks of WS-* specifications that have been ratified by standards bodies and moved away from defacto standards worked on behind closed doors. As the OASIS announcement states, there were abstaining voters:
The ballot for approval of Web Services Transaction Version 1.1 as OASIS Standard, announced at [1], was completed
with sufficient affirmative votes to approve the specification. However, because there were negative votes, the Web
Services Transaction (WS-TX) Technical Committee was required to decide how to proceed, per the OASIS TC Process (at
[2]). The TC gave consideration to the negative votes but has voted to request the specification be approved. (See [3].)

     We are pleased, therefore, to announce that Web Services Transaction Version 1.1 has been approved as an OASIS
Standard. The submission of the approved standard can be found at [4].

     Congratulations to the TC, and the community of implementers, developers and users who have brought the work
successfully to culmination.
It is not clear why Sun abstained, but Fujitsu were worried about some of the references in the specifications to other standards/specifications being out-of-date. We believe the technical committee will update the references where appropriate.

There have been several articles articles on the history of extended transactions. One more to add to the list comes from the co-chair of the WS-TX committee, where he traces the roots of WS-TX back to the CORBA Activity Service:
The origins of WS-Coordination are in the CORBA Activity service, which itself was the result of an OMG request for proposals to specify Additional Structuring Mechanisms for the OTS Specification.
Who said Web Services is all about reinventing the wheel?
  • This article is part of a featured topic series on SOA

No comments

Watch Thread Reply

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.