When you deploy entities from J2EE archives, EAServer creates a class loader to match the entity name and configures the entities to use the new class loader. You can configure class loaders using the Management Console or an Ant configuration script.
Configuring class loaders in the Management Console
Connect to the server with the Management Console—see Chapter 2, “Management Console Overview.”
Expand the Class Loaders folder. Existing class loader definitions display.
To create a new class loader, right-click the Class Loaders folder and choose Add. Follow the pages in the Add wizard to create the new class loader.
To modify an existing class loader, click its icon to display the properties in the details pane, modify the settings, then click OK to save the changes.
Table 10-1 describes the class loader properties.
Using Ant to configure class loaders
Create an Ant configuration file or identify
one already in your project where you can add the class loader configuration
to the configure target. For
more information, see Chapter
2, “Ant-Based Configuration,” in the EAServer Automated Configuration Guide.
Add or configure the class loader by invoking the setProperties task
from the configure or configure-user
target. For example:
<setProperties classLoader="ejbjar-sample"> <property name="classPath" value="~/ejbjars/*.jar"/> <property name=”parentFist” value=”true”/> <property name=”parentClassLoader” value=”app-sample”/> <property name="classloaderImpl" value="com.sybase.djc.util.NamedClassLoader"/> </setProperties>
Table 10-1 describes the class loader properties.
