hello Edward,
Thank you for your patience.
I thought that the situation was worst than that! Thank you for your
(detailled) help. It is now clear like crystal water ;)
Cheers,
Sacha
> -----Message d'origine-----
> De : [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]De la part de Kenworthy, Edward
> Envoyé : lundi, 5 février 2001 11:29
> À : 'jBoss'
> Objet : RE: [jBoss-User] IsA behaviour when inheriting beans
>
>
> Sacha
>
> OK to get an EJB entity bean instance I have to:
>
> Get its home interface
> Ask the home interface for a specific instance
> I get back a remote interface.
>
> If I have, say, 3 classes:
> SimpleCustomer
> CorporateCustomer extends SimpleCustomer
> RetailCustomer extends SimpleCustomer
> =>CorporateCustomerHome extends SimpleCustomerHome etc etc
>
> If EJBland supported inheritance I should be able to do the following
> without any extra coding:
>
> lookup SimpleCustomerHome and call a finder on it that gives me back a
> collection of all matching instances of SimpleCustomer, RetailCustomer and
> CorporateCustomer.
>
> It doesn't.
>
> If I want it to do this I have to implement the finder methods of
> SimpleCustomer to ALSO lookup RetailCustomer and
> CorporateCustomer. And if I
> add a new sub-class of SimpleCustomer then I have to modify
> SimpleCustomer's
> finder methods to handle the new sub-class. The parent has to
> know about its
> children - a pain to develop and a maintenance nightmare.
>
> If however you are willing to code this all yourself and do it completely
> (and don't forget to map it to the underlying DB correctly) then you can
> have "proper" inheritance. (Oh and don't forget, you shouldn't really use
> normal java casting for remote objects).
>
> Hope this is clear now, cos I ain't going to go into any more detail :-)
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
