[jboss-jira] [JBoss JIRA] (DROOLS-628) DecisionTable incorrectly parsed

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/DROOLS-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010662#comment-13010662 ] 

RH Bugzilla Integration commented on DROOLS-628:
------------------------------------------------

Mario Fusco <mfusco at redhat.com> changed the Status of [bug 1150308|https://bugzilla.redhat.com/show_bug.cgi?id=1150308] from ASSIGNED to MODIFIED

> DecisionTable incorrectly parsed 
> ---------------------------------
>
>                 Key: DROOLS-628
>                 URL: https://issues.jboss.org/browse/DROOLS-628
>             Project: Drools
>          Issue Type: Bug
>            Reporter: Mario Fusco
>            Assignee: Mario Fusco
>             Fix For: 6.2.0.CR1
>
>
> 5.2.0.CR1 creates incorrect drl from decision table. With 5.1.0.M1 the drl for the same decision table is correct.
> Wrong DRL from 5.2.0.CR1:
> rule "ProcessState"
> salience 65522
> ruleflow-group "CompleteSubOrder"
> activation-group "ProcessState"
> when
> $m:ModifiedMarker(processState==null, state ==null)
> $s:SubOrder
> then
> $m.setIsModified(true);
> $s.setProcessState(ProcessState.CREATED);
> end
> Correct DRL with 5.1.0.M1:
> rule "ProcessState"
> salience 65522
> ruleflow-group "CompleteSubOrder"
> activation-group "ProcessState"
> when
> $m:ModifiedMarker()
> $s:SubOrder(processState==null, state ==null)
> then
> $m.setIsModified(true);
> $s.setProcessState(ProcessState.CREATED);
> end
> The difference is that the constraints are put to $m instead of putting them to $s.
> The behaviour in 5.2.0.CR1 is the same for all decision tables in my project and prevents me from upgrading to newer drools versions.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)