Question
Charles Schwab
US
Last activity: 25 Sep 2024 10:49 EDT
Error generating library after importing custom JARs - "Error(s) detected while generating java. The import cannot be resolved"
I'm upgrading some old JARs in my application and running into these errors when trying to save/generate one of the libraries - all the jars and classes its referencing are the old jars:
Error(s) detected while generating java. Compiler reported: ---------- 1. ERROR in /com/pegarules/generated/our_library.java (at line 28) import old.jar.package.client.SecurityToken; ^^^^^^^^^^^^^ The import 'the.old.jar' cannot be resolved ----
So far I've followed the steps here for uploading custom/external jars: Importing custom Java archives or classes into a CodeSet (pega.com)
- Imported new external JAR's (via Distribution -> Import) and added them to our custom Customer codeset version 07-01-01 (previous JAR libraries are in 06-01-01
- Updated/saved "properties/com.pega.pegarules.bootstrap.codeset.version.Customer/default" DSS to 07-01-01 to match new custom codeset
- Updated DSS "compiler/defaultPaths" (via Configure > System > Settings > Compiler) to reference the new libraries
- Restarted websphere profile
- Queried pr_engineclasses table and verified the new JARs are showing under the new codeset version
I also updated some data pages that reference classes from the new JARs so I know it's seeing them, but now in updating this library/associated function I'm getting these errors. Any ideas?