I noticed in the EJB 1.1 specification that declarative isolation levels
have been removed. I've got some questions about this.
1) What is the motivation behind removing delcarative isolation? I found it
to be very useful in EJB 1.0.
2) If I have a container-managed persistent entity bean, the EJB
specification says the container will automatically handle isolation. How
does the container magically know what isolation level to use? Does the
deployer need to somehow inform the container about the correct isolation
level to use?
2.1) If so, how does the deployer know what the correct isolation level
should be? The deployer may not know anything about the internal
transactional requirements of the deployed distributed application. How
should the application assembler communicate isolation requirements to the
deployer? Isn't this error prone?
2.2) Doesn't this mean we need to re-specify isolation over and over again
each time an app is deployed?
--
Ed Roman
CEO, The Middleware Company
Author, "Mastering Enterprise JavaBeans and the Java 2 Platform, Enterprise
Edition"
(published by John Wiley & Sons, 1999)
http://www.middleware-company.com
[EMAIL PROTECTED]
512-346-7994
===========================================================================
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".
