simplicity & portability; BMT is implied in the concept of BMP, so BMT in
ejb 1.0 applied only to CMP, but could render CMP beans non portable(for
instance, not every isolation level is supported by every RDBMS). You can
still manage your transactions manually with BMP, but generally it doesn't
make much sense to do so with CMP; you're best off with a facade made by a
session bean that can either manage its own transactions or one that
benefits from declarative transactions, and declarative transactional
behavior can be modified by the assembler or the deployer.
HTH
JP
> -----Original Message-----
> From: Samuel Abraham [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 27, 2001 12:18 AM
> To: [EMAIL PROTECTED]
> Subject: Bean Managed Transactions
>
>
> Hi,
> Why was Bean Managed Transactions disallowed for Entity beans
> after EJB1.0
> while
> it was still kept for Session beans?
> Any idea...
> TIA
> sam
>
> ______________________________________________________________
> ___________
> Get Your Private, Free E-mail from MSN Hotmail at
http://www.hotmail.com.
===========================================================================
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".
