xmlBlaster - Requirement engine.transaction

REQUIREMENT

engine.transaction

Type NEW

Priority MEDIUM

Status OPEN

Topic XmlBlaster supports transactions built on the CORBA OTS/JTS service

Des
cription This is a collection of thoughts about MOM Transactions from our mailing list
JINI transactions
Possibly the JINI transactions are the most suitable framework for xmlBlaster.
General transaction ability of xmlBlaster

2 phase commit

long transactions

commit, rollback, recovery etc mechanisms

nested transactions (to complicated to use for everyday problems?)

XA-Support
How to become an XA-ResourceManager?
Find several transaction monitors/managers with XA-Support to test with.
OTS-support
How to become a transactional object?
Compare transaction functionality with other MOM

Transactional queues (IBM's MQSeries, BEA's MessageQ)

Transactional publish and subscribe (Tuxedos EventBroker)

Transactional Conversations

Perhaps we should implement a little TP-Monitor to test our implementation (in fact we need a tool to load balance multiple xmlBlaster servers).
MOM transactions span across companies or the internet. So we need to be controllable by external TP monitors.
Maybe MOM will loosely couple together flat transactions from different locations by providing the persistent queue part 'D' of the 'ACID'.

Configure
NOTE: Configuration parameters are specified on command line (-someValue 17) or in the xmlBlaster.properties file (someValue=17). See requirement "util.property" for details.
Columns named Impl tells you if the feature is implemented.
Columns named Hot tells you if the configuration is changeable in hot operation.

This page is generated from the requirement XML file xmlBlaster/doc/requirements/engine.transaction.xml

Back to overview

Topic	XmlBlaster supports transactions built on the CORBA OTS/JTS service
Des cription	This is a collection of thoughts about MOM Transactions from our mailing list JINI transactions Possibly the JINI transactions are the most suitable framework for xmlBlaster. General transaction ability of xmlBlaster 2 phase commit long transactions commit, rollback, recovery etc mechanisms nested transactions (to complicated to use for everyday problems?) XA-Support How to become an XA-ResourceManager? Find several transaction monitors/managers with XA-Support to test with. OTS-support How to become a transactional object? Compare transaction functionality with other MOM Transactional queues (IBM's MQSeries, BEA's MessageQ) Transactional publish and subscribe (Tuxedos EventBroker) Transactional Conversations Perhaps we should implement a little TP-Monitor to test our implementation (in fact we need a tool to load balance multiple xmlBlaster servers). MOM transactions span across companies or the internet. So we need to be controllable by external TP monitors. Maybe MOM will loosely couple together flat transactions from different locations by providing the persistent queue part 'D' of the 'ACID'.
Configure	NOTE: Configuration parameters are specified on command line (-someValue 17) or in the xmlBlaster.properties file (someValue=17). See requirement "util.property" for details. Columns named Impl tells you if the feature is implemented. Columns named Hot tells you if the configuration is changeable in hot operation.