> -----Original Message-----
> From: Kenneth D. Litwak [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 23, 2000 7:19 PM
> To: [EMAIL PROTECTED]
> Subject: Transaction completion
>
>
> If method A class mehod B, and method B's transaction attribute is
> "REQUIERD", (as just one possible scenario), how does the
> container know when to
> end the transaction? MOre generally,
>
> a) since stateful session beans can hae a CMT-based
> transaction span
> multiple methods, how does the container know when the
> transaction should end?
When the method that invoked the transaction ends, the transaction will be
committed
Ulf Gohde
> b) I thought that an entity bean could not have a
> transaction span multiple
> methods.
who says that? it's a legal and good design setting the entity bean methods
to TX-REQUIRED and wrap all client access to them in session beans. How else
would you wrap updates to multiple properties in one transaction (that's the
sense of transactions at all, isn't it).
> So how could any transaction attribute besdies
> REQUIED_NEW be legal?
> REQUIRED and MANDATOREY allow or require a method touse a
> trnsaction which
> already exists, which violates he idea of an entity bean
> having to execute one
> mehtod in the scope of one transation, not multiple methods.
>
> WOuld someone pelase clarify this for me? Thanks.
>
>
> Ken
>
> ==============================================================
> =============
> 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".
