EJB transactions are handle by a distributed transaction monitor (JTS,
which can be implemented on top of the CORBA OTS for example).
The JDBC connections are resource managers in this scenario, and each bean
could have its own, esp. if the run in different VMs. JTS handles that.
Note however, that two phase commits pose a problem with most JDBX drivers,
unless they are JDBC 2.0/XA compliant. If you have only one data source
you can get away with a JDBC 1.0 driver in what is sometimes referred to a
1.5
phase commit.
Frank Sauer
The Technical Resource Connection
Tampa, FL
http://www.trcinc.com
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Steve Roth
> Sent: Tuesday, March 28, 2000 3:49 PM
> To: [EMAIL PROTECTED]
> Subject: Entity Beans-- Shared Connections
>
>
> Question:
>
> When an EJB Entity bean calls another EJB Entity bean, is it
> important that
> they both share the same database Connection?
>
> More specifically, is it important that the 2nd Entity EJB
> sees the same
> transactional view of the database?
>
> How does this work when the EJB Server is replicated and each
> Entity EJB can
> be running in a different server?
>
> Thanks
> -Steve Roth, [EMAIL PROTECTED]
>
> ==============================================================
> =============
> 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".
