Hi all,
Pardon my transactional ignorance, but if an EJB server claims to have an
XA interface (as defined by the X/Open consortium), how many of the below
can I assume?
a) that 2PC client-demarcated transactions can be begun, using the XA interface
b) that 2PC transactions are automatically done for my EJB's which declare
transactional attributes in it's descriptor
c) that the EJB server claiming to have this interface also includes the
transaction manager, and I don't have to buy a separate transaction manager
What is the relation between XA and JTA anyway? Why would I use one and
not the other?
Thanks for your knowledge and time,
David Bullock
PS. I know there are performance issues with 2PC, but I am wanting to
wrapper a non-transactional data-source with a Session bean.
--
David Bullock
Systems Architect - LISA Corporation
38 Greenhill Rd, Wayville S.A. 5034
http://www.lisa.com.au/
mailto:[EMAIL PROTECTED]
phone: +61 8 8271 1555
fax: +61 8 8271 1199
===========================================================================
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".
