JBoss Transactions Documentation Library: General
Some background reading.
Approaching Web Services Transactions. This article analyzes two Web services transaction proposals that are currently being developed. One is from OASIS and another proposed by IBM, Microsoft, and BEA.
Introducing WS-Coordination. This article introduces the underlying concepts of Web Services Coordination, and shows how a generic coordination framework can be used to provide the foundations for higher-level business processes. In future articles, we will demonstrate how coordination allows us to move up the Web services stack to encompass WS-Transaction and on to BPEL4WS.
Introducing WS-Transaction, Part 1. This article introduces the first publicly available WS-Coordination-based protocol - Web Services Transaction - and shows how WS-Transaction provides atomic transactional coordination for Web services.
Introducing WS-Transaction, Part 2. This article looks at support for extended transactions across Web services. We also show how these can be used to provide the basis for higher-level business process management and workflow technology.
A comparison of Web services transaction protocols. Up to August 2003 there were two contenders for the Web services transaction space: OASIS Business Transactions Protocol (BTP), and the Web Services Transactions (WS-Tx) specification. There have been several subjective articles and comments comparing BTP to WS-Tx, attempting to show that BTP can do everything WS-Tx can and ignoring the important differences that exist. This article will try to give an objective comparison of these two specifications and show how they both attempt to address the problems of running transactions with Web services.
Introducing WS-CAF. Web services have become the integration platform of choice for enterprise applications. Those applications by the very nature of their enterprise-scale components can be complex in structure, which is compounded by the need to share common data or context across business processes supported by those applications. Those processes may be very long lived, and may contain periods of inactivity, for example, where constituent services require user interactions.
Transactions in the world of Web services, Part 1.This paper presents and illustrates a high-level overview of the Web service specifications for WS-Coordination and WS-Transaction.
Transactions in the world of Web services, Part 2.This paper presents and illustrates a high-level overview of the Web service specifications for WS-Coordination and WS-Transaction.
Coordinating Web Services Activities with WS-Coordination, WS-AtomicTransaction, and WS-BusinessActivity.Understand how the new WS-BusinessActivity specification relates to the WS-AtomicTransaction and WS-Coordination specifications. These specifications collectively provide the necessary mechanisms to create activities, join in activities, and reach common agreement on the outcome of joint operations across distributed systems.
Secure, Reliable, Transacted Web Services: Architecture and Composition.In addition to basic message interoperability and interface exchange, developers increasingly require that higher-level application services interoperate. Many commercial applications execute in an environment ("middleware" or "operating systems") that provide support for functions like security and transactions. This paper provides a succinct overview for the set of Web service specifications that address these needs.
Context, Coordinators, and Transactions - The Importance of WS-CAF.Eric Newcomer discusses the OASIS Web Services-Composite Application Framework (WS-CAF) which defines a new and unique context management service for composite Web services applications, and enhances related Web services coordination and transaction specifications such as WS-T and WS-C.
XML Transactions for Web Services, Part 1.This three part series of articles describes and demonstrates transactional web services, elaborates why and when we may require web service transactions, and explains how WS-Coordination and WS-Transaction address the transactional requirements of web services.
XML Transactions for Web Services, Part 2.This article discusses and demonstrates the operation of atomic transactions in web services.
XML Transactions for Web Services, Part 3.This article discusses another type of XML transaction, the Business Activity (BA).
Transaction Specification documents.This specification describes coordination types that are used with the extensible coordination framework described in the WS-Coordination specification. It defines two coordination types: Atomic Transaction (AT) and Business Activity (BA).
Latest forum discussions
- Re: Whether we should hande RuntimeExceptions arising from badly behaved XAResource implementations
- Sep 17, 2014 7:08 AM by Tom Jenkinson
- As there doesn't app…
- Re: Integrate IJ Tracer and NTA tool
- Sep 16, 2014 9:41 AM by Jesper Pedersen
- You may be intereste…
- Bringing Transactional Guarantees to MongoDB: Part 1
- May 28, 2014 6:07 AM by Paul Robinson
- In this blog post I'…
- Research Worth Knowing on CAP & ACID
- May 27, 2014 3:57 PM by Mark Little
- The last couple of b…
- View more latest news
- EJ-Technologies has kindly provided free JProfiler licenses.
- JetBrains has kindly donated an open source IntelliJ license.
- Syncro Soft has kindly provided free <oXygen/> XML Editor licenses.