posted 16 years ago
The container/server has to implement the stubs and skeletons for the Remote interface of the EJB. The stub resides on the client machine and delegates the method call to the skeleton, which resides in the container. The skeleton interprets the parameters sent to it, and delegates the call to the appropriate business method in the EJB. One of the ways a container can implement this skeleton is to extend the EJB class, and have the method call delegate to the superclass. If the business methods are declared final, the container can no longer extend the EJB class to implement the skeleton. Of course, the skeleton can be implemented in other ways, but I guess Sun decided to leave the decision to the J2EE app.servers.