My interpretation of this part of the spec is merely that only "session"
beans with bean-managed transaction demarcation can programmatically control
transaction isolation levels. Transaction isolation levels for all other
beans is controlled via the deployment descriptor. This does not mean that
tx isolation levels no longer apply to entity beans, it means that the
container sets the isolation level for them via the values set in the DD.
John Zerbe - Mellon Bank
Information Technology Solutions - Middleware Team
Phone: 412-234-1048 E-Mail:[EMAIL PROTECTED]
> -----Original Message-----
> From: Sriram Narayan (CTS) [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, September 26, 2000 5:35 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Are isolation levels not applicable to 1.1 entity beans?
>
> ...reposting in the hope of getting some answers.
> any hint will do.
> thanks
> Hi
> The revision history section(C.5) of the 1.1 spec say this :
>
> "The scope of the EJB specification for managing transaction isolation
> levels was reduced to sessions with bean-managed transaction demarcation.
> The current EJB specification does not have any API for managing
> transaction
> isolation for beans with container-managed transaction demarcation (note
> that all Entity beans fall into this category)."
>
> ... which means, unlike in 1.0, tx isolation levels no longer apply to
> entity beans and CMT session beans.
>
> Could someone pls tell the reason for this change?
> If this is left unspecified, does the container define the behaviour?
>
> thanks
> sriram
> Cognizant Technology Solutions - Pune.
>
> This e-mail and any files transmitted with it are for the sole use of the
> intended recipient(s) and may contain confidential and privileged
> information.
> If you are not the intended recipient, please contact the sender by reply
> e-mail and destroy all copies of the original message.
> Any unauthorised review, use, disclosure, dissemination, forwarding,
> printing or copying of this email or any action taken in reliance on this
> e-mail is strictly
> prohibited and may be unlawful.
>
> Visit us at http://www.cognizant.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".
