> -----Original Message-----
> From: Richard Monson-Haefel [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, May 08, 2001 18:38
> To: [EMAIL PROTECTED]
> Subject: EJB 2.0: Local Interfaces and Transactions/Secrutiy
>
>
> 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.
I believe interception is still required, to load the bean if it is not in
the cache, etc. Also, the container could optimize the 'supports' case while
still supporting (?) the other cases.
>
> 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.
>
Same as above.
- Avi
--
And now for something completely different.
===========================================================================
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".
