Steve,
Ideally the beans share the same connection. If they end up distributed it
is of course important that your server support distributed transactions.
<vendor>
In GemStone/J we provide "colocation" policies that force the beans to run
in the same address space. The JDBC connection pooling mechanism is
transction aware and allocates the same underlying DB connection to beans
running in the same transaction.
</vendor>
-Chris.
> -----Original Message-----
> From: Steve Roth [SMTP:[EMAIL PROTECTED]]
> 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".
