We would like to understand whether the EJB specification
defines/supports/prohibits transactions that cross container
boundaries, and, if so, how such transactions are coordinated. If a
transaction can span multiple containers/servers, which
container/server is considered to be the Transaction Coordinator?
We would also like to know whether such transactions could be carried
out among containers provided by multiple vendors, and what protocol
they would use to coordinate such transactions.
If not defined in the specification, are there vendors that are
solving this problem? How are they doing this?
Can CORBA objects participate in transactions coordinated by an EJB
Server? Can EJB components participate in transactions coordinated on
the CORBA side?
Which of the ACID transaction properties are being (can be)
preserved/guaranteed for global transactions (within a container and
across container boundaries), given that serializability of local
transactions doesn't imply serializability of global transactions? We
know that atomicity is easy to achieve (via the two-phase commit
protocol) - what about the other properties?
Mark
_______________________________________________________________________
Mark Feblowitz 40 Sylvan Road
Senior Principal Member of Technical Staff Waltham, MA 02451-1128
GTE Laboratories Incorporated [EMAIL PROTECTED]
(617) 466-2947, fax (617) 466-2618
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
