B2B Integration 10.5 | Administering and Monitoring B2B Transactions | Integration Server Administrator's Guide | Class Loading in Integration Server | Adding Classes to the Server Classpath | Class Searching Order
 
Class Searching Order
When a Java service refers to a class, Integration Server will, by default, look for the referenced class in this order:
1. On the server classpath.
2. Locally, within the package.
3. In all required packages.
When a class is found, Integration Server immediately loads and uses the class.
You can change the class loading order by modifying a package's manifest.v3 file to use the package class loader:
<value name='classloader'>package</value>
When a package's classloader property is "package", the class loading order is as follows:
1. Locally, within the package.
2. In all required packages.
3. On the server classpath.
The default value for the classloader property is "system". That is what Integration Server uses when no value is set for the classloader property:
<value name='classloader'/>
For detailed information about configuring a package to use the package class loader, see Using a Package Class Loader.
Copyright © 2016- 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.