The main reason for this is to prevent the EJB class from mistakenly
being called directly rather than through its remote interface. If this
were done, the container is taken out of the loop - this breaks the
component model.
EJB allows the class to inherit its remote interface for those who
prefer this style; it does not require it for the reason above.
-- Mark
"Andy L. Czerwonka" wrote:
>
> Question. The bean class implements the bean's functionality. The remote
> interface defines the interface. Why doesn't the bean class implement the
> remote interface? I must have methods presented in the remote interface, so
> why doesn't it just implement it?
>
> _____________________
> Andy L. Czerwonka
> CORBATECH Inc.
> (403) 547-8892
>
> ===========================================================================
> 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".
