Question
accenture
IN
Last activity: 17 Oct 2016 21:46 EDT
Java package cant be resolved getting "com.atl cannot be resolved to a type" errorI am trying to use my custom made java code in prpc
I am trying to use my custom made java code in prpc I performed following step(Using 7.2 server)
1. placed jar files in lib folder
2. Updated the compiler / defaultpaths with the path of jar files
3. Updated the compile/default classes.
4. refreshed external jars
5. tried to lookup java classes from SMA and I am able to locate them
While running getting below error:
Failed to compile generated Java com.pegarules.generated.activity.ra_action_consolidatedxmlactivity_flowaction_f1a8042f6d5460702a00e8e5d2dc7379: ---------- 1. ERROR in \com\pegarules\generated\activity\ra_action_consolidatedxmlactivity_flowaction_f1a8042f6d5460702a00e8e5d2dc7379.java (at line 938) com.atl.nova.pega.integration.FlowActionIntegrator flowactionintegator = new com.atl.nova.pega.integration.FlowActionIntegrator();
Thanks
***Updated by Moderator: Marissa. Removed user added #helpme and Ask the Expert group tags. Apologies for confusion, shouldn't have been an end-user option***
accenture
IN
Adding full Error: Failed to compile generated Java com.pegarules.generated.activity.ra_action_consolidatedxmlactivity_flowaction_f1a8042f6d5460702a00e8e5d2dc7379: ---------- 1. ERROR in \com\pegarules\generated\activity\ra_action_consolidatedxmlactivity_flowaction_f1a8042f6d5460702a00e8e5d2dc7379.java (at line 938) com.atl.nova.pega.integration.FlowActionIntegrator flowactionintegator = new com.atl.nova.pega.integration.FlowActionIntegrator(); ^^^^^^^ com.atl cannot be resolved to a type
EPAM Systems, Inc.
ES
Hi,
Please review the below link once,
Just to confirm whether you have re-started JVM or not?
This is usually the result of a rule resolution issue where the wrong copy of the pzAssemblePreprocess activity was run. This has been seen a number of times and frequently seems to result from "corrupt" / "incomplete" entries in the database cache tables associated with rule resolution. There are about 10 tables associated with this process and if they get "out of sync" with each other this can be the result. All of the related tables need to be truncated at the same time - clearing only some of them causes more trouble.
Truncating below table may fix problem at your end.
delete from pr4_rule where pzInsKey like '%CSSINCLUDE%';
truncate table pr_sys_appcache_dep;
truncate table pr_sys_appcache_entry;
truncate table pr_sys_appcache_shortcut;
truncate table pr_sys_app_hierarchy_flat;
truncate table pr_sys_app_ruleset_index;
truncate table pr_sys_cache_entry;
truncate table pr_sys_class_ancestors;
truncate table pr_sys_cache_dep;
truncate table pr_sys_cache_impl;
truncate table pr4_rule_sysgen;
truncate table pr_assembledclasses;
Kindly let me know, if it helps you.
Thanks,
Asif