Troubleshooting
Problem
The package-level classloader fails; folder does not exist
Have created a package that requires a class in package_name>\code\classes\<classfolder>\<classfolder>\<class name>.
When the package's manifest.v3 is set so that the classloader used is "package" (<value name='classloader'>package</value>), IS does not know how to find the classes in \code\classes folder... specifically, \code\classes\IntegrationFWSvcs\ExtensionFramework\ folder.
Following error is seen:
"!ENTRY com.softwareag.is.ui.javaserviceeditor 4 0 2015-04-09 10:51:11.253
!MESSAGE C:\SoftwareAG\IntegrationServer\instances\default\packages\ClassLoaderTest\code\source\ClassLoaderTest.java:12: error: package IntegrationFWSvcs.ExtensionFramework does not exist
import IntegrationFWSvcs.ExtensionFramework.RuleParameter;
^
C:\SoftwareAG\IntegrationServer\instances\default\packages\ClassLoaderTest\code\source\ClassLoaderTest.java:36: error: cannot find symbol
RuleParameter parameter = new RuleParameter(
^
symbol: class RuleParameter
location: class ClassLoaderTest
C:\SoftwareAG\IntegrationServer\instances\default\packages\ClassLoaderTest\code\source\ClassLoaderTest.java:36: error: cannot find symbol
RuleParameter parameter = new RuleParameter(
^
symbol: class RuleParameter
location: class ClassLoaderTest
3 errors"
With classloader set to package, in Designer, when editing Java service after loading the classes in Project Workspace, it gives the class not found error when saving.
If manifest.v3 is changed to use the server class loader, there are no errors. It works if the classloader is set to server.
Document Location
Worldwide
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
20 March 2025
UID
ibm17219684