The concept of Local interfaces in EJB 2.0 hold a great deal of promise
for allowing entity beans become more granular and more performant, but
there are a couple of modifications that should be made with regard to
transaction and security attributes. These modifications would ensure
that these interfaces fulfill their high performance promise.
1.
The specification should require that Local interfaces use only the
"Supports" transaction attribute. The Supports Tx attribute simply
propagates the callers (always another bean for local calls)
transaction. This eliminates the overhead of intercepting the call for
the purpose of evaluating the Tx context according to the Tx attribute.
2.
The specification should require that the security identity attribute of
the Local interface be propagated from the caller. It should not be
allowed to use a runAs security identity. Again this reduces the
overhead of delegating calls from the LocalEJBObject to the bean
instance since the security principal doesn't change.
Informed feedback is welcome.
Thanks,
Richard
--
Richard Monson-Haefel
Author of Enterprise JavaBeans, 2nd Edition (O'Reilly 2000)
Co-Author of Java Message Service (O'Reilly 2000)
http://www.jMiddleware.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".
