[ http://jira.codehaus.org/browse/DROOLS-430?page=comments#action_50185 ]
Matthias Gommeringer commented on DROOLS-430: --------------------------------------------- I'm having the same problem and looked at the source code in method "org.drools.io.RuleHandler.startRule()": It seems to be a copy/paste bug in line 159 where the "ruleDesc" value is used to initialize the XorGroup of the java "rule" object. > xor-group directive seems to be ignored > --------------------------------------- > > Key: DROOLS-430 > URL: http://jira.codehaus.org/browse/DROOLS-430 > Project: drools > Type: Bug > Environment: Windows XP > java version "1.5.0_04" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05) > Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode) > Reporter: Sascha Coenen > Assignee: bob mcwhirter > Attachments: rules.xml > > > I used the jsr-94 API to create a StatelessRuleSession, registered the > rule.xml file which I attached and fed in the strings "hello" and "world" as > in-params. > Although I declared the two rules within the attached file to belong to the > same xor-group, both rules get fired upon execution: > output of my test-application: > [java] Starting Application > [java] URL for rule file file:///C:\dev\projects\rule-test/meta/rules.xml > [java] Service provider created > [java] Ruleset registered > [java] rule sesssion created > [java] Rule ONE fired. > [java] Rule TWO fired. > To my understanding, only rule ONE should be fired because both rules belong > to the same XOR-group. Maybe I'm missing something but I also ran tests using > the xor-group attribute in combination with other attributes like salience, > no-loop etc. but couldn't produce the desired effect of mutually exclusive > rules. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
