The "right" way to implement SOAP transactions is
to define a standard protocol for a SOAP runtime to communicate with a
transaction management coordinator and to use a standard SOAP header to
convey transaction context. IBM/MSFT/BEA jointly developed and published the
WS-Coordination and WS-Transaction specifications, which address these
requirements, but at this point there is no formal standardization effort
tackling this issue. It's possible that the OASIS WS-BPEL effort will do it,
because many BPEL use cases require transaction coordination.
You might take a look at IBM's BPWS4J. It's based
on Axis, and I think it supports transactions. You might also take a look at
Collaxa. It's also based on Axis, it implements BPEL4WS, and I believe it
supports transactions.
Anne
|
- Distributed Transaction with AXIS David payam
- Re: Distributed Transaction with AXIS Anne Thomas Manes
- Re: Distributed Transaction with AXIS David payam