Thanks for your reply. In answer to your question...
> > Second, does inheritance of Session Beans, work the same as other
> > inheritance in Java? The answer is probably yes, but I've
> > never seen this
> > covered. Every EJB I've seen has extended EjbObject. Can I still have
> > abstract super classes?
>
>Certainly you can derive from your own abstract base classes, as long as
>they derive from EJBObject. Out of curiosity, why do you want to do
>this?
In our web-based application all users see a common log-on screen, and
after their authentication, based on their user role, we redirect them to
the appropriate user interface. To represent that I envisioned having a
"SessionManager" Statefull Session bean, which would govern what was
possible based on that user's role. It would encapsulate other entity
beans, representing the other people and application objects that the
logged in user is allowed to participate with. In accordance with what I
think is good OO designed, I pictured having "SessionManager" as abstract,
and deriving sub-classes based on user roles. In the case of my domain,
health care, there might be a PatientSessionManager, a
PhycisianSessionManager, and ClericalSessionManager. By doing this I can
store the commonality (of which there are a few) in the super class. I
think the case for inheritance amongst business logic is pretty strong.
-adamw
