Just going through some old emails . . . The answer to this is that entity beans inherit the default isolation level of the resource being accessed, which, if a database, is often READ_COMMITTED. So I think that if you want to tweak the isolation level for you entity beans, you'd have to modify the RDBMS default. I believe I learned this from the spec you're quoting. Otherwise I picked it up from the J2EE Developer's Guide section on transactions: http://java.sun.com/j2ee/j2sdkee/techdocs/guides/ejb/html/DevGuideTOC.html Scott Stirling Allaire Corporation http://www.allaire.com/developer/jrunreferencedesk/ > -----Original Message----- > From: Sriram Narayan (CTS) [mailto:[EMAIL PROTECTED]] > Sent: Saturday, September 23, 2000 3:44 PM > To: [EMAIL PROTECTED] > Subject: [EJB-INT] Are isolation levels not applicable to 1.1 entity > beans? > > > 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. =========================================================================== 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".
