> >
> > I'm in favor of eliminating overhead from the container's checking of
> > transaction and security contexts, but I don't think "Supports" is
> > appropriate for EJB 2.0 CMP entity beans with local component
> > interfaces. These must always execute within a transaction (see
> > e.g. EJB 2.0 PFD2 17.4.1), which "Supports" would not ensure.
>
> You are absolutely correct. I'll change my proposal to "Mandatory". This
> then requires that there be some checking for context, which is fast and
> can be avoided with pre-compiling, but it makes sense to require that a
> transaction be present.
meaning that you would require SessionBean local interfaces to be executed in
a transaction context which doesn't make sense or do you mean only local
interfaces for entity beans (you didn't explicitly mention that)?
Regards,
Robert
>
> --
> 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".
===========================================================================
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".
