The standard locations for deploying Java and EJB component class files is the java/classes directory. EAServer also generates the component’s stubs and skeleton classes under this directory.
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 as specified in “Calling local interface methods”.
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.
Component-specific JAR files should be deployed in the EAServer java/classes subdirectory and added to the custom class list.
To configure the custom list, follow the instructions in “Configuring an entity’s custom class list”.
JNDI classes
EAServer never custom loads the standard Java Naming and Directory
(JNDI) packages. In EAServer versions prior to 4.0, an EJB component
required the following in the custom class list:
com.sybase.ejb.*;javax.naming.*;javax.naming.spi.*
In EAServer 4.0 and later, these classes and interfaces are ignored when listed in the custom class list.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
