Bean inheritence is not covered explicitly in the spec. As a result, various
EJB server's ability to facilitate this is somewhat uneven, and there are
some issues with trying to get to real polymorphism.
There is quite a bit about this topic in the archives. In particular there
is a useful post here:
http://archives.java.sun.com/cgi-bin/wa?A2=ind9912&L=ejb-interest&F=&S=&P=48
190, titled "Steps for how to do Entity Inheritance"
So I didn't mean to say that it is not allowed, but it is not a good idea
per se.
-Chris.
> -----Original Message-----
> From: J. Matthew Pryor [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, March 29, 2000 1:49 PM
> To: [EMAIL PROTECTED]
> Subject: Re: OO Analysis and Design for EJB Systems
>
> > -----Original Message-----
> > From: A mailing list for Enterprise JavaBeans development
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Chris Raber
> > Sent: Wednesday, March 29, 2000 7:20 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: OO Analysis and Design for EJB Systems
> >
> >
> > Class diagrams are still germane. Just because you don't have
> > implementation
> > inheritance
>
> [snip]
>
> What are the limiting factors for implementation inheritance ?
>
> I agree that interface inheritance is crucial for good design, but
> aggregation can make you life hell when doing O/R mappings
>
> Thanks,
> Matthew
>
> ==========================================================================
> =
> 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".
