Custom class lists for EJB components

When you deploy EJB components, classes from the EJB-JAR file are expanded in one of these locations:

• If you are deploying a standalone EJB-JAR file, this directory in the EAServer installation, where ejbjar is the base name of the EJB-JAR file:

  deploy/ejbjars/ejbjar
  

• If you are deploying an EJB-JAR file inside an EAR file, this directory in the EAServer installation, where ear is the base name of the EAR file and ejbjar is the base name of the EJB-JAR file:

  deploy/ejbjars/ear/ejbjar
  

EAServer generates the component’s stub and skeleton classes in the same location.

A Java component’s implementation class and stub classes are automatically part of the custom class list for the component. Add the following additional classes to the custom list:

• Stub classes used for intercomponent calls. For EJB local interface calls, you must also configure sharing of the class instances between the calling entity and the called component.

• Other classes that your component loads and passes as parameters or return values for intercomponent calls, or passes to clients as method return values and output parameter values.

• For EJB components, classes that extend javax.naming.InitialContext or other javax.naming classes and that are called by your component.

• Additional classes that must be reloaded when the component is refreshed. For example, if you are debugging utility classes used by the component, add these classes to the custom list.

Deploy component-specific JAR files in an EAServer subdirectory, such as java/classes, and add them to the custom class list.