satya,
xa drivers are primarily for:
- 2P Commit & recoverable transactions
- monitoring & managing transactions
- updates spanning multiple (possibly heterogenous) databases
of course you need a transaction manager that
can take advantage of the XA features of jdbc 2.0
if you do not need the above features, you might
be better off with jdbc 1.x drivers (& datasources).
(which do support transactions and 1PC)
to answer your question, if you have the autoCommit
turned on (Connection.setAutoCommit/getAutoCommit),
then your updates will be executed & committed as
individual transactions. If auto commit is turned off,
then you need to explicitly commit/rollback a group
of transactions.
by default, the autoCommit is turned on for new connections.
the jdbc topic is quite vast, and i would suggest you
read up on articles/tips on the java sun site.
-krish
----- Original Message -----
From: Komatineni, Satya <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, May 15, 2001 2:07 PM
Subject: Is it mandatory to have XADataSource for EJB transactional suppor
t?
> If I am manipulating a database through SLSBs via non-xa datasources,
would
> the transaction automatically commited by the EJB container (assuming I
have
> the transaction required attribute set)?
>
> Or do I need to have XA driver supporting the datasource to have this
> functionality.
>
> Your help is much appreciated
> Satya
>
>
===========================================================================
> 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".
>
>
===========================================================================
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".
