Yes encapsulation and delegation is the correct way to implement inheritance in EJB.
Yahooooooooooo!!!! Almost-real OO is now on the server side. If all goes as planned, we should start seeing very sophisticated and feature-rich apps coming out of the J2EE world. And they will be built much more quickly.
Thank you for the response.
I think you are overly excited about OO, but I have been proven wrong many times before.
Possibly overly excited - sorry about potential over-exuberance.
??? But this relates to my original reason for my post - i.e. IS THIS DELEGATED-INHERITANCE (GIVEN THE J2EE CONTAINER TECHNOLOGIES) A DANGEROUS APPROACH (FOR PERFORMANCE) IN JBOSS ???
My intent is to code significantly (not purely) from an OO perspective. Object graphs (which result in significantly normalized DB schemas) would help immensely to maintain very complex biz logic. Then, intend to DE-normalize DB (and flatten object graph) as performance bottlenecks rear their ugly heads. Going in this direction (OO -> flat) is much easier during development than having flat and unmanageable spaghetti code. Just like the old rules for writing assembly - make it WORK first - THEN optimize.
LUV 2 HEAR WHAT U THINK (ANY OTHERS' INTELLIGENT DIALOG ALSO APPRECIATED)