[jboss-jira] [JBoss JIRA] Resolved: (JBRULES-3083) DecisionTable incorrectly parsed with 5.2.0.CR1

[Mark Proctor (JIRA)]

     [ https://issues.jboss.org/browse/JBRULES-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Proctor resolved JBRULES-3083.
-----------------------------------

    Fix Version/s: 5.2.0.Final
       Resolution: Rejected


This is not a bug, the decision table is formed incorrectly. Add ModifiedMarker to it's own Condition column that is NOT shared with SubOrder.

> DecisionTable incorrectly parsed with 5.2.0.CR1
> -----------------------------------------------
>
>                 Key: JBRULES-3083
>                 URL: https://issues.jboss.org/browse/JBRULES-3083
>             Project: Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.2.0.CR1
>            Reporter: Kara Melba
>            Assignee: Mark Proctor
>             Fix For: 5.2.0.Final
>
>         Attachments: decisiontable.jpg
>
>
> 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 attached jpg contains the decision table snippet.
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira