Classpaths are viewed differently in WAS 7 than in WAS 6. I added the correct classpaths from Advisor 6.7 into the manifest files in my RAD 7.5 projects and everything is working correctly.
Hi, I am facing same issue while migrating to WAS 7, it is working fine with WAS 6.0. Please help me understand how the classpath reference by WAS 7 differently and what changes I need to make in the Classpath.
For our application, Blaze Jars present in the WEB-INF/lib.
execution of the Blaze Rule Project :: Service 'EditEnrich'. Server 'Deployed Rule Server' on host 'dkcrv051.svr.emea.jpmchase.net'.com.blazesoft.server.base.NdServerRuntimeException: Failure initializing an agent for project /apps/im_Refresh/configuration/rules/editenrich/EditEnrich.adv.com.blazesoft.engines.rules.NdResourceInitializationException: There were 131 exceptions while initializing the Java class provider resource.-------- 1com.blazesoft.engines.rules.java.NdJavaClassImportResourceException: com.blazesoft.util.NdWrappedRuntimeException: com.blazesoft.engines.rules.NdResourceException: Exception adding support Java class to the Java class provider resource.com.blazesoft.engines.rules.java.NdRelatedJavaClassImportException:While importing the 'boolean equals(Object)' method of the 'java.lang.Object' class.
Retrieving data ...