[ http://jira.jboss.com/jira/browse/JBRULES-1613?page=all ] Michael Katai updated JBRULES-1613: ----------------------------------- Description: In one special case, the naming of two functions in the drl-File causes an error. Here my code (simplified): package.... import .... rule ... when .... then checkHierachyInstance(...); end function void checkHierachyInstance(...) { checkHierachyInstanceRecursive(...); } function void checkHierachyInstanceRecursive(...) { } [ checkHierachyInstance : Function Compilation error checkHierachyInstance (line:54): The method checkHierachyInstanceRecursive(Activity, SActivity, int, int) is undefined for the type CheckHierachyInstance ] Rule Compilation error : [Rule name=action_conditional_starttimereached, agendaGroup=MAIN, salience=0, no-loop=false] action_conditional_starttimereached_5491408023587370397/Rule_action_conditional_starttimereached_0.java (15:857) : The import action_conditional_starttimereached_5491408023587370397.CheckHierachyInstance cannot be resolved action_conditional_starttimereached_5491408023587370397/Rule_action_conditional_starttimereached_0.java (20:1531 ) : The method checkHierachyInstance(String, Consumer, Activity, SActivity, String) is undefined for the type Rule_actio n_conditional_starttimereached_0 [ checkHierachyInstance : Function Compilation error checkHierachyInstance (line:54): The method checkHierachyInstanceRecursive(Activity, SActivity, int, int) is undefined for the type CheckHierachyInstance ] As far as i have found out, the error occurs ONLY if I append any character to the functionname "checkHierachyInstance", in my case the word "Recursive". It works if I use a completely different name instead of "checkHierachyInstanceRecursive" or exchange a character in "checkHierachyInstanceRecursive". For example I can use "function void myFunc(...)" or "function void checkHierachyInstancRecursive(...)" instead of "checkHierachyInstanceRecursive" . The only combination of function names i'm not allowed to use is checkHierachyInstance and checkHierachyInstanceXXX was: In one special case, the naming of two functions in the drl-File causes an error. Here my code (simplified): package.... import .... rule ... when .... then checkHierachyInstance(...); end function void checkHierachyInstance(...) { checkHierachyInstanceRecursive(...); } function void checkHierachyInstanceRecursive(...) { } [ checkHierachyInstance : Function Compilation error checkHierachyInstance (line:54): The method checkHierachyInstanceRecursive(Activity, SActivity, int, int) is undefined for the type CheckHierachyInstance ] Rule Compilation error : [Rule name=action_conditional_starttimereached, agendaGroup=MAIN, salience=0, no-loop=false] action_conditional_starttimereached_5491408023587370397/Rule_action_conditional_starttimereached_0.java (15:857) : The import action_conditional_starttimereached_5491408023587370397.CheckHierachyInstance cannot be resolved action_conditional_starttimereached_5491408023587370397/Rule_action_conditional_starttimereached_0.java (20:1531 ) : The method checkHierachyInstance(String, Consumer, Activity, SActivity, String) is undefined for the type Rule_actio n_conditional_starttimereached_0 [ checkHierachyInstance : Function Compilation error checkHierachyInstance (line:54): The method checkHierachyInstanceRecursive(Activity, SActivity, int, int) is undefined for the type CheckHierachyInstance ] As far as i have found out, the error occurs ONLY if I append anything character to the functionname "checkHierachyInstance", in my case the word "Recursive". It works if I use a completely different name instead of "checkHierachyInstanceRecursive" or exchange a character in "checkHierachyInstanceRecursive". For example i can use "function void myFunc(...)" or "function void checkHierachyInstancRecursive(...)" instead of "checkHierachyInstanceRecursive" . The only combination of function names i'm not allowed to use is checkHierachyInstance and checkHierachyInstanceXXXXX -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBRULES-1613?page=comments#action_12415616 ] Brandon Chapman commented on JBRULES-1613: ------------------------------------------ Ignore my comment. It seems the issue is similar but the underlying cause is not the same. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBRULES-1613?page=com.atlassian.jira.p... ] Edson Tirelli updated JBRULES-1613: ----------------------------------- Fix Version/s: 5.0.0.CR1 (was: 5.0.0.M3) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBRULES-1613?page=com.atlassian.jira.p... ] Mark Proctor updated JBRULES-1613: ---------------------------------- Summary: functions fail when other functions that start with the same name exist (was: In one special case, the naming of a Drools-Function causes an error) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira