extension mechanism and classloading


EJB design: extension mechanism and classloading

  1. extension mechanism and classloading (1 messages)

    I read a statement:
    "Support for the extension mechanism does not exist for EAR, WAR, or RAR applications as defined in the J2EE specification, since these applications are not directly loaded by a ClassLoader instance."

    Can someone explain the different in the classloading mechanism of JAR files and the others?
    Am new to EJB;and hence excuse me if this is too trivial a concept.
  2. extension mechanism and classloading[ Go to top ]


    J2EE servers use multiple class loaders, largely because this allows dynamic application reloading. Clearly we don't want to reload all the application server's own classes on redeploying an application. This would mean that the application server would always need to be restarted. So application servers use different class loaders for application code to those they use for their own standard libraries, for example. Typically one or more new class loaders will be created for each application deployed on a server.
    Using EJBs considerably complicates the deployment model, compared to that for a pure web application. This is also true of class loading. In a WAR, we can simply include all binary dependencies in the /WEB-INF/lib directory. However, things get more complicated when WARs access EJBs.

    Nabil BENMIRA