U can use any kind of inheritance with EJB as normal classes . But it must
satisfy the EJB requirements. For eg. If you are making the entity beans ur
entity class must implement entity interface along with it you can have the
normal super class also. the entity interface can be indirect also.
So either you can logically break your remote functions in different
interfaces, or you can have one interface declaring all the functions.
Implement those functions in the superclass and extend this in ur entity
class.
Regards
Ashwani Kalra
E-Comm Group
NIIT Ltd. India
> ----------
> From: Edward Barrett[SMTP:[EMAIL PROTECTED]]
> Reply To: A mailing list for Enterprise JavaBeans development
> Sent: Friday, July 14, 2000 5:32 PM
> To: [EMAIL PROTECTED]
> Subject: Entity bean inheritance
>
> I wonder if someone can suggest how I would model the following within
> EJBs.
>
> A client can have many investments, some in stocks, some in cash, some in
> other things. Most investments have the same business methods and
> therefore in a normal OO design I would propose an Investment interface or
> super class (depending on how similar the functionality implementations
> were) and sub classes for each investment type.
>
> How can I implement using interfaces or inheritance in Entity beans - I'm
> specifically thinking of generic home interfaces, inheritance within
> remote interfaces / stubs, etc.
>
> Or can this just not be done in EJB ?
>
> TIA
>
> Ed
>
> ==========================================================================
> =
> 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".
