You can configure custom class lists for your servers, applications, Web applications, packages, and components, and so forth using the Java Classes tab in the EAServer Manager properties for the entity. If using jagtool or an EAServer XML configuration file, configure the class list by setting the entity property that ends in .java.classes, for example the application property name is com.sybase.jaguar.application.java.classes.
Custom class lists for entities that are deployed in
J2EE archives
When you import entities from J2EE archives such as EJB-JAR,
EAR, or WAR files, EAServer configures the custom class list to
include the classes included in the archive. You do not need to
configure the class list in most cases. EAServer ignores java.classes properties
set in the archive’s sybase-easerver-config.xml file
(if present). If you must customize these properties, do so after deploying
the J2EE archive.
Configuring the custom class list for a server,
application, Web application, component, or Web component in EAServer
Manager
Display the properties dialog for the server, application, Web application, component, package, or servlet.
Display the Java Classes tab.
If necessary, configure the delegation order as described in “The class loader hierarchy and delegation policy”.
Edit the class list as follows:
To add a class, click Add and edit the name of the class, package, or JAR file, following the value syntax rules described below.
To rearrange the order of listed items, highlight the item to be moved in the list and click Move Up or Move Down.
To remove an item, click Remove.
Value syntax for Java class lists Enter a comma-separated list of Java classes, packages, and JAR files. You can specify all classes in a package using wildcards, as in this example:
com.xyz.MyPackage.*
You can specify all classes in a JAR file by specifying the JAR file name, as in this example:
MyEntityBean.jar
JAR files must be deployed in the EAServer java/classes subdirectory.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
