Hello Sven,
> I cannot for the likes of me imagine something like
> 'table inheritance' in a database. For what I understand is that you
> want to create subsets of entity beans that contain different
> combinations of fields in the DB.
I do not care on how the data will be persisted (OODBMS, RDBMS, flat file,
...). Using a tool and BMP to represent class inheritance is not a problem.
>From the thread going yesterday (Cedric Beust, ...), I think what I really
wanted is Component inheritance (and not class or interface inheritance),
which is not possible!
> I guess that could be done using the little example I gave yesterday.
> Let's consider you have a to create this payment process. You would
...
> 5) EDIPaymentBean (Implementation)
...
> Looking up payment/Bank and calling create on the returned HomeInterface
> would result in a BankPaymentBean being instantiated and remote.pay()
> would get your payment efectuated by bank.
The same with entity beans would be a good start! Thank you for your
example, I think this kind of scheme is interesting.
...
> have access to the implementation of the algorithms (or using tricky
> > delegation on the server side).
>
> Take a look also at a thread here about reflection. Might be interesting .
I've read it. Interesting. Nevertheless, using BMP and O/R mapping tool
(like Castor, Cocobase, Top-link, ...) seems a very near solution and more
flexible (the schema can change independently from class structure)
thank you for your help. Cheers,
Sacha
===========================================================================
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".
