I am not very sure, but I think the following is the reason,
The explicit transaction management is not a very easy task. In EJB 1.0
days, when the programmer had the liberty to do this, many a times, the
transaction management was either done wrongly or done inefficiently.
It was realised that by adding another transaction attribute (Never) to the
earlier existing 5 attributes used for container managed transaction
demarcation, it would be possible to provide anything and everything that
the bean developer might want to do in the explicit transaction management.
And EJB1.1 did just that...
Gurus, please correct me if I am wrong..
Shelly
----- Original Message -----
From: Yagiz Erkan <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 17, 2001 5:57 PM
Subject: Bean Managed Transactions in Entity Beans
> Hi all,
>
> EJB 1.0 allows Entity Beans to bean-manage its transactions. And this is
> not allowed when it comes to EJB 1.1. What's the reason behind this?
> Thanks,
> Regards,
>
> Yagiz
>
>
===========================================================================
> 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".
===========================================================================
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".
