User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
I don't understand the advantage of a default EJB implementation with
AOP over a solution with pure OOP.
In "Enterprise Aspect-Oriented Programming with AspectJ"
(http://newaspects.com/presentations/) it is suggested to implement
empty EJB callback methods using AspectJ. An interface is used that
implements the methods. With declare parents all SessionBeans are
advised to implement this interface.
What is the advantage of this implementation? I can do the same thing
with a simple OOP super class as well. My Beans just extend this super
(Ok, with the AOP-interface-solution multiple inheritance is possible.
But that is no convincing argument to me. I don't need multiple
inheritance in my EJBs.)