How do I Configure Classloaders?

The Deploy Service provides the following default behavior:

• One classloader for each application
• Classloader used for Web Components is the child classloader of the ejb/.rar components

To set a single classloader for multiple applications, modify the enabled attribute for the <single-classloader-for-applications> tag to true. This means that a single classloader can now be used for multiple applications as specified in the <application-group> attribute specified below.

The Deploy Service provides for application groups where a group of applications share the same classloader. Any number of groups can then be declared. Absence of any groups after enabling single application classloader would mean a universal application group where all applications share the same classloader. Any application not in the <application-group> attribute specified below gets its own classloader if no groups are specified.

<single-classloader-for-applications enabled="true">
  <!--sample application group definition -->
  <!--application-group apps="abcd.ear,xyz.jar" -->
  <!--any app not in the list above, will get its own classloader. If no groups are specified, a single classloader is used for all applications.-->
<single-classloader-for-applications>

• How to Configure Deployment Settings
• Auto Deploy Directory Properties
• Validation Properties
• Compiler Properties
• Application Versioning
• Startup Hooks
• Application Hooks

© Pramati Technologies 2007	Runs on Pramati Server | Feedback | Legal