This is exactly what I'm doing. I cut and paste the same behavior
into each EJB, then add the "implements MyInterface" phrase to the remote
interface definition. Although this works, it is silly not to be able to
inherit method behavior as well as method signature when one so desires.
-Charles May
> >>> Posting number 17543, dated 9 Nov 2000 19:28:46
> Date: Thu, 9 Nov 2000 19:28:46 +0530
> Reply-To: A mailing list for Enterprise JavaBeans development
> <[EMAIL PROTECTED]>
> Sender: A mailing list for Enterprise JavaBeans development
> <[EMAIL PROTECTED]>
> From: Rahul Aras <[EMAIL PROTECTED]>
> Subject: Re: Cannot inherit methods ... ?
> MIME-Version: 1.0
> Content-Type: text/plain; charset="iso-8859-1"
>
> Why are going for a superclass??
>
> Why dont you put those methods in an interface?? Say XYZ
>
> ...and while publishing your remote methods , just make your bean's remote
> interface extend EJBObject interface as well the XYZ interface. Remember
> that you CAN extend more than one interface.
>
> -- Rahul
>
>
*****************************************************************
DISCLAIMER: The information contained in this e-mail may be confidential
and is intended solely for the use of the named addressee. Access, copying
or re-use of the e-mail or any information contained therein by any other
person is not authorized. If you are not the intended recipient please
notify us immediately by return e-mail to the originator.
===========================================================================
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".
