>From a response on the Weblogic ejb newsgroup:
<snip>
DataSource does not do "global transactions" so each time your entity bean
uses a DataSource by calling getConnection(), they (potentially) get a
different connection. As a result, each bean method invocation is done in a
separate transaction (unless you are passing the connection between
methods). TxDataSource understands JTS transactions and associates a single
database connection with the JTS transaction. As a result, each bean method
that gets invoked in the scope of JTS transaction ends up using the same
database connection so that the actual database transaction has the same
scope as the JTS transaction.
</snip>
HTH
Lee
_________________________________
Lee Turner
Systems Developer
Information Technology Leeds
_________________________________
Watt Gilchrist Ltd
Ring Road, West Park
Leeds, LS16 6RA
Tel: 0113 288 3200
Fax: 0113 275 1690
http://www.wattgilchrist.co.uk
_________________________________
> -----Original Message-----
> From: Riccardo F. [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, March 27, 2001 11:32 AM
> To: [EMAIL PROTECTED]
> Subject: TXDataSource
>
> Somebody can help me to understand the exact difference between DataSource
> and TXDataSource in weblogic reality, for use a connection pool?
>
> Thanks in advance.
>
> Riccardo.
>
> ----------------------------------------------
> Virgilio Mail - Il tuo indirizzo E-mail gratis
> http://mail.virgilio.it
>
> ==========================================================================
> =
> 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".
