Laird Nelson wrote:
> Now, my only remaining (quite humble at this point, believe me!)
> questions are:

Humble is good; it keeps one on the edge. ;-)

> 1. The specification makes a distinction between component inheritance,
> implementation inheritance, and interface inheritance.  None of these
> three terms is well defined in the specification.  Nevertheless, the
> specification permits the latter two (see page 290).  What kind of
> inheritance is the kind you list above, and is your interpretation in
> keeping with the specification?

He showed component inheritance. Yes, component inheritance is not
supported. It is one of things that are being considered for EJB2.0
(AFAIK anyway).

> 2. Suppose I am able to solve the problem you state above (out of band,
> i.e. with my own classes).  Is that the only issue with respect to
> various kinds of inheritance in EJB?  I personally cannot think of any
> others (other than implementation-type issues, such as lazy- versus
> eager-loading of complex object graphs).

The problem is with finders. You will find it impossible to implement
component inheritance properly without the help from the EJB-container.
It's not something you can just add "on top".

/Rickard

--
Rickard �berg

@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.dreambean.com
Question reality

===========================================================================
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".

Reply via email to