[JBoss JIRA] Created: (JBRULES-2257) Wrong condition evaluation if the condition contains a variable assignment
5:44 p.m.
Wrong condition evaluation if the condition contains a variable assignment
----------------------------------------------------------------------------
Key: JBRULES-2257
URL: https://jira.jboss.org/jira/browse/JBRULES-2257
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.0.1.FINAL
Environment: Mac OS X, iMac, Eclipse Galileo (3.5)
Reporter: Udo Klinkmüller
Assignee: Mark Proctor
I have a rule which checks variables of two equal objects in an old and a new version. If
I work with the variable daclaration $nd1 then the consequence is NOT executed although it
should.
This is the version of the rule in that the consequence is not executed although it
should:
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
TestObject( $nd1: date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+ $nd1
+" ...");
results.add($nto);
end
------------------------------------------
This is the rule version which delivers the expected result (without using $nd1):
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
$nto: TestObject( date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+
$nto.getDate1() +" ...");
results.add($nto);
end
------------------------------------------
--
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
5:48 p.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2257) Wrong condition evaluation if the condition contains a variable assignment
[
https://jira.jboss.org/jira/browse/JBRULES-2257?page=com.atlassian.jira.p...
]
Udo Klinkmüller updated JBRULES-2257:
-------------------------------------
Description:
I have a rule which checks variables of two equal objects in an old and a new version. If
I work with the variable daclaration $nd1 then the consequence is NOT executed although it
should.
This is the version of the rule in that the consequence is not executed although it
should:
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
TestObject( $nd1: date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+ $nd1
+" ...");
results.add($nto);
end
------------------------------------------
This is the rule version which delivers the expected result (without using $nd1):
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
$nto: TestObject( date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+
$nto.getDate1() +" ...");
results.add($nto);
end
------------------------------------------
If wished, I have a corresponding JUnit test case for this issue.
was:
I have a rule which checks variables of two equal objects in an old and a new version. If
I work with the variable daclaration $nd1 then the consequence is NOT executed although it
should.
This is the version of the rule in that the consequence is not executed although it
should:
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
TestObject( $nd1: date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+ $nd1
+" ...");
results.add($nto);
end
------------------------------------------
This is the rule version which delivers the expected result (without using $nd1):
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
$nto: TestObject( date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+
$nto.getDate1() +" ...");
results.add($nto);
end
------------------------------------------
Wrong condition evaluation if the condition contains a variable
assignment
----------------------------------------------------------------------------
Key: JBRULES-2257
URL: https://jira.jboss.org/jira/browse/JBRULES-2257
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core
Affects Versions: 5.0.1.FINAL
Environment: Mac OS X, iMac, Eclipse Galileo (3.5)
Reporter: Udo Klinkmüller
Assignee: Mark Proctor
I have a rule which checks variables of two equal objects in an old and a new version. If
I work with the variable daclaration $nd1 then the consequence is NOT executed although it
should.
This is the version of the rule in that the consequence is not executed although it
should:
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
TestObject( $nd1: date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+ $nd1
+" ...");
results.add($nto);
end
------------------------------------------
This is the rule version which delivers the expected result (without using $nd1):
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
$nto: TestObject( date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+
$nto.getDate1() +" ...");
results.add($nto);
end
------------------------------------------
If wished, I have a corresponding JUnit test case for this issue.
--
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
6:54 a.m.
New subject: [JBoss JIRA] Commented: (JBRULES-2257) Wrong condition evaluation if the condition contains a variable assignment
[
https://jira.jboss.org/jira/browse/JBRULES-2257?page=com.atlassian.jira.p...
]
Mark Proctor commented on JBRULES-2257:
---------------------------------------
assignment and evaluation on the same field is not supported, you should bind it, then
separate it with a "," when you want to add an evaluator for it.
Wrong condition evaluation if the condition contains a variable
assignment
----------------------------------------------------------------------------
Key: JBRULES-2257
URL: https://jira.jboss.org/jira/browse/JBRULES-2257
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core
Affects Versions: 5.0.1.FINAL
Environment: Mac OS X, iMac, Eclipse Galileo (3.5)
Reporter: Udo Klinkmüller
Assignee: Mark Proctor
Fix For: 5.1.0.M2
I have a rule which checks variables of two equal objects in an old and a new version. If
I work with the variable daclaration $nd1 then the consequence is NOT executed although it
should.
This is the version of the rule in that the consequence is not executed although it
should:
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
TestObject( $nd1: date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+ $nd1
+" ...");
results.add($nto);
end
------------------------------------------
This is the rule version which delivers the expected result (without using $nd1):
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
$nto: TestObject( date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+
$nto.getDate1() +" ...");
results.add($nto);
end
------------------------------------------
If wished, I have a corresponding JUnit test case for this issue.
--
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
6:54 a.m.
New subject: [JBoss JIRA] Closed: (JBRULES-2257) Wrong condition evaluation if the condition contains a variable assignment
[
https://jira.jboss.org/jira/browse/JBRULES-2257?page=com.atlassian.jira.p...
]
Mark Proctor closed JBRULES-2257.
---------------------------------
Fix Version/s: 5.1.0.M2
Resolution: Won't Fix
Wrong condition evaluation if the condition contains a variable
assignment
----------------------------------------------------------------------------
Key: JBRULES-2257
URL: https://jira.jboss.org/jira/browse/JBRULES-2257
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core
Affects Versions: 5.0.1.FINAL
Environment: Mac OS X, iMac, Eclipse Galileo (3.5)
Reporter: Udo Klinkmüller
Assignee: Mark Proctor
Fix For: 5.1.0.M2
I have a rule which checks variables of two equal objects in an old and a new version. If
I work with the variable daclaration $nd1 then the consequence is NOT executed although it
should.
This is the version of the rule in that the consequence is not executed although it
should:
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
TestObject( $nd1: date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+ $nd1
+" ...");
results.add($nto);
end
------------------------------------------
This is the rule version which delivers the expected result (without using $nd1):
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
$nto: TestObject( date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+
$nto.getDate1() +" ...");
results.add($nto);
end
------------------------------------------
If wished, I have a corresponding JUnit test case for this issue.
--
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
4:22 p.m.
New subject: [JBoss JIRA] Reopened: (JBRULES-2257) Wrong condition evaluation if the condition contains a variable assignment
[
https://jira.jboss.org/jira/browse/JBRULES-2257?page=com.atlassian.jira.p...
]
Edson Tirelli reopened JBRULES-2257:
------------------------------------
Assignee: Edson Tirelli (was: Mark Proctor)
As discussed with Mark, this is a valid case and assignments+constraints should work fine.
My guess is that there is a bug when using it in conjunction with "||". I will
look into it.
Wrong condition evaluation if the condition contains a variable
assignment
----------------------------------------------------------------------------
Key: JBRULES-2257
URL: https://jira.jboss.org/jira/browse/JBRULES-2257
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core
Affects Versions: 5.0.1.FINAL
Environment: Mac OS X, iMac, Eclipse Galileo (3.5)
Reporter: Udo Klinkmüller
Assignee: Edson Tirelli
Fix For: 5.1.0.M2
I have a rule which checks variables of two equal objects in an old and a new version. If
I work with the variable daclaration $nd1 then the consequence is NOT executed although it
should.
This is the version of the rule in that the consequence is not executed although it
should:
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
TestObject( $nd1: date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+ $nd1
+" ...");
results.add($nto);
end
------------------------------------------
This is the rule version which delivers the expected result (without using $nd1):
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
$nto: TestObject( date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+
$nto.getDate1() +" ...");
results.add($nto);
end
------------------------------------------
If wished, I have a corresponding JUnit test case for this issue.
--
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
9:32 p.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2257) Wrong condition evaluation if the condition contains a variable assignment
[
https://jira.jboss.org/browse/JBRULES-2257?page=com.atlassian.jira.plugin...
]
Edson Tirelli updated JBRULES-2257:
-----------------------------------
Fix Version/s: 5.1.0.CR1
(was: 5.1.0.M2)
Wrong condition evaluation if the condition contains a variable
assignment
----------------------------------------------------------------------------
Key: JBRULES-2257
URL: https://jira.jboss.org/browse/JBRULES-2257
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core
Affects Versions: 5.0.1.FINAL
Environment: Mac OS X, iMac, Eclipse Galileo (3.5)
Reporter: Udo Klinkmüller
Assignee: Edson Tirelli
Fix For: 5.1.0.CR1
I have a rule which checks variables of two equal objects in an old and a new version. If
I work with the variable daclaration $nd1 then the consequence is NOT executed although it
should.
This is the version of the rule in that the consequence is not executed although it
should:
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
TestObject( $nd1: date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+ $nd1
+" ...");
results.add($nto);
end
------------------------------------------
This is the rule version which delivers the expected result (without using $nd1):
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
$nto: TestObject( date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+
$nto.getDate1() +" ...");
results.add($nto);
end
------------------------------------------
If wished, I have a corresponding JUnit test case for this issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:44 p.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2257) Wrong condition evaluation if the condition contains a variable assignment
[
https://jira.jboss.org/browse/JBRULES-2257?page=com.atlassian.jira.plugin...
]
Mark Proctor updated JBRULES-2257:
----------------------------------
Fix Version/s: 5.1.0
(was: 5.1.0.CR1)
Wrong condition evaluation if the condition contains a variable
assignment
----------------------------------------------------------------------------
Key: JBRULES-2257
URL: https://jira.jboss.org/browse/JBRULES-2257
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core
Affects Versions: 5.0.1.FINAL
Environment: Mac OS X, iMac, Eclipse Galileo (3.5)
Reporter: Udo Klinkmüller
Assignee: Edson Tirelli
Fix For: 5.1.0
I have a rule which checks variables of two equal objects in an old and a new version. If
I work with the variable daclaration $nd1 then the consequence is NOT executed although it
should.
This is the version of the rule in that the consequence is not executed although it
should:
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
TestObject( $nd1: date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+ $nd1
+" ...");
results.add($nto);
end
------------------------------------------
This is the rule version which delivers the expected result (without using $nd1):
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
$nto: TestObject( date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+
$nto.getDate1() +" ...");
results.add($nto);
end
------------------------------------------
If wished, I have a corresponding JUnit test case for this issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:27 p.m.
New subject: [JBoss JIRA] Commented: (JBRULES-2257) Wrong condition evaluation if the condition contains a variable assignment
[
https://jira.jboss.org/browse/JBRULES-2257?page=com.atlassian.jira.plugin...
]
Michael Paitl commented on JBRULES-2257:
----------------------------------------
I have a following rule which worked as expected in version 4(4.0.3) but is not working in
version 5 (5.0.1 or 5.1.0-SNAPSHOT):
rule "Test rule"
when
Message($var1:prop1 matches "^[6,7,9]$" , $var2:prop2 matches
"^[1]$" || $var3:prop3 matches "^[1]$", $var4:prop4 not matches
"^(.{0})$" )
then
System.out.println( "Message is not displayed for prop1='6' ,
prop2='', prop3='', prop4='1' in v4 but is in v5" );
end
However, if i remove variable assignment from either prop2 or prop3 e.g.
rule "Test rule"
when
Message($var1:prop1 matches "^[6,7,9]$" , prop2 matches "^[1]$" ||
$var3:prop3 matches "^[1]$", $var4:prop4 not matches "^(.{0})$" )
then
System.out.println( "Message is not displayed for prop1='6' ,
prop2='', prop3='', prop4='1' in both v4 and v5 " );
end
then both V4 and V5 will not display the message
Wrong condition evaluation if the condition contains a variable
assignment
----------------------------------------------------------------------------
Key: JBRULES-2257
URL: https://jira.jboss.org/browse/JBRULES-2257
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core
Affects Versions: 5.0.1.FINAL
Environment: Mac OS X, iMac, Eclipse Galileo (3.5)
Reporter: Udo Klinkmüller
Assignee: Edson Tirelli
Fix For: 5.1.0.FINAL
I have a rule which checks variables of two equal objects in an old and a new version. If
I work with the variable daclaration $nd1 then the consequence is NOT executed although it
should.
This is the version of the rule in that the consequence is not executed although it
should:
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
TestObject( $nd1: date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+ $nd1
+" ...");
results.add($nto);
end
------------------------------------------
This is the rule version which delivers the expected result (without using $nd1):
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
$nto: TestObject( date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+
$nto.getDate1() +" ...");
results.add($nto);
end
------------------------------------------
If wished, I have a corresponding JUnit test case for this issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:18 a.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2257) Wrong condition evaluation if the condition contains a variable assignment
[
https://jira.jboss.org/browse/JBRULES-2257?page=com.atlassian.jira.plugin...
]
Edson Tirelli updated JBRULES-2257:
-----------------------------------
Fix Version/s: 5.2.0.M1
(was: 5.1.0.FINAL)
Wrong condition evaluation if the condition contains a variable
assignment
----------------------------------------------------------------------------
Key: JBRULES-2257
URL: https://jira.jboss.org/browse/JBRULES-2257
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core
Affects Versions: 5.0.1.FINAL
Environment: Mac OS X, iMac, Eclipse Galileo (3.5)
Reporter: Udo Klinkmüller
Assignee: Edson Tirelli
Fix For: 5.2.0.M1
I have a rule which checks variables of two equal objects in an old and a new version. If
I work with the variable daclaration $nd1 then the consequence is NOT executed although it
should.
This is the version of the rule in that the consequence is not executed although it
should:
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
TestObject( $nd1: date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+ $nd1
+" ...");
results.add($nto);
end
------------------------------------------
This is the rule version which delivers the expected result (without using $nd1):
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
$nto: TestObject( date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+
$nto.getDate1() +" ...");
results.add($nto);
end
------------------------------------------
If wished, I have a corresponding JUnit test case for this issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:34 a.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2257) Wrong condition evaluation if the condition contains a variable assignment
[
https://issues.jboss.org/browse/JBRULES-2257?page=com.atlassian.jira.plug...
]
Mark Proctor updated JBRULES-2257:
----------------------------------
Fix Version/s: 5.2.0.CR1
(was: 5.2.0.M1)
Wrong condition evaluation if the condition contains a variable
assignment
----------------------------------------------------------------------------
Key: JBRULES-2257
URL: https://issues.jboss.org/browse/JBRULES-2257
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core
Affects Versions: 5.0.1.FINAL
Environment: Mac OS X, iMac, Eclipse Galileo (3.5)
Reporter: Udo Klinkmüller
Assignee: Edson Tirelli
Fix For: 5.2.0.CR1
I have a rule which checks variables of two equal objects in an old and a new version. If
I work with the variable daclaration $nd1 then the consequence is NOT executed although it
should.
This is the version of the rule in that the consequence is not executed although it
should:
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
TestObject( $nd1: date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+ $nd1
+" ...");
results.add($nto);
end
------------------------------------------
This is the rule version which delivers the expected result (without using $nd1):
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
$nto: TestObject( date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+
$nto.getDate1() +" ...");
results.add($nto);
end
------------------------------------------
If wished, I have a corresponding JUnit test case for this issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:36 p.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2257) Wrong condition evaluation if the condition contains a variable assignment
[
https://issues.jboss.org/browse/JBRULES-2257?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-2257:
--------------------------------------
Fix Version/s: 5.2.0.CR2
(was: 5.2.0.CR1)
Wrong condition evaluation if the condition contains a variable
assignment
----------------------------------------------------------------------------
Key: JBRULES-2257
URL: https://issues.jboss.org/browse/JBRULES-2257
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core
Affects Versions: 5.0.1.FINAL
Environment: Mac OS X, iMac, Eclipse Galileo (3.5)
Reporter: Udo Klinkmüller
Assignee: Edson Tirelli
Fix For: 5.2.0.CR2
I have a rule which checks variables of two equal objects in an old and a new version. If
I work with the variable daclaration $nd1 then the consequence is NOT executed although it
should.
This is the version of the rule in that the consequence is not executed although it
should:
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
TestObject( $nd1: date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+ $nd1
+" ...");
results.add($nto);
end
------------------------------------------
This is the rule version which delivers the expected result (without using $nd1):
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
$nto: TestObject( date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+
$nto.getDate1() +" ...");
results.add($nto);
end
------------------------------------------
If wished, I have a corresponding JUnit test case for this issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8 p.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2257) Wrong condition evaluation if the condition contains a variable assignment
[
https://issues.jboss.org/browse/JBRULES-2257?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-2257:
--------------------------------------
Fix Version/s: 5.3.0.Beta1
(was: 5.2.0.Final)
Wrong condition evaluation if the condition contains a variable
assignment
----------------------------------------------------------------------------
Key: JBRULES-2257
URL: https://issues.jboss.org/browse/JBRULES-2257
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core
Affects Versions: 5.0.1.FINAL
Environment: Mac OS X, iMac, Eclipse Galileo (3.5)
Reporter: Udo Klinkmüller
Assignee: Edson Tirelli
Fix For: 5.3.0.Beta1
I have a rule which checks variables of two equal objects in an old and a new version. If
I work with the variable daclaration $nd1 then the consequence is NOT executed although it
should.
This is the version of the rule in that the consequence is not executed although it
should:
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
TestObject( $nd1: date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+ $nd1
+" ...");
results.add($nto);
end
------------------------------------------
This is the rule version which delivers the expected result (without using $nd1):
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
$nto: TestObject( date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+
$nto.getDate1() +" ...");
results.add($nto);
end
------------------------------------------
If wished, I have a corresponding JUnit test case for this issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:42 p.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2257) Wrong condition evaluation if the condition contains a variable assignment
[
https://issues.jboss.org/browse/JBRULES-2257?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-2257:
--------------------------------------
Fix Version/s: 5.3.0.CR1
(was: 5.3.0.Beta1)
Wrong condition evaluation if the condition contains a variable
assignment
----------------------------------------------------------------------------
Key: JBRULES-2257
URL: https://issues.jboss.org/browse/JBRULES-2257
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core
Affects Versions: 5.0.1.FINAL
Environment: Mac OS X, iMac, Eclipse Galileo (3.5)
Reporter: Udo Klinkmüller
Assignee: Edson Tirelli
Fix For: 5.3.0.CR1
I have a rule which checks variables of two equal objects in an old and a new version. If
I work with the variable daclaration $nd1 then the consequence is NOT executed although it
should.
This is the version of the rule in that the consequence is not executed although it
should:
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
TestObject( $nd1: date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+ $nd1
+" ...");
results.add($nto);
end
------------------------------------------
This is the rule version which delivers the expected result (without using $nd1):
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
$nto: TestObject( date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+
$nto.getDate1() +" ...");
results.add($nto);
end
------------------------------------------
If wished, I have a corresponding JUnit test case for this issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:04 a.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2257) Wrong condition evaluation if the condition contains a variable assignment
[
https://issues.jboss.org/browse/JBRULES-2257?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-2257:
--------------------------------------
Fix Version/s: 5.3.0.Final
(was: 5.3.0.CR1)
Wrong condition evaluation if the condition contains a variable
assignment
----------------------------------------------------------------------------
Key: JBRULES-2257
URL: https://issues.jboss.org/browse/JBRULES-2257
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core
Affects Versions: 5.0.1.FINAL
Environment: Mac OS X, iMac, Eclipse Galileo (3.5)
Reporter: Udo Klinkmüller
Assignee: Edson Tirelli
Fix For: 5.3.0.Final
I have a rule which checks variables of two equal objects in an old and a new version. If
I work with the variable daclaration $nd1 then the consequence is NOT executed although it
should.
This is the version of the rule in that the consequence is not executed although it
should:
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
TestObject( $nd1: date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+ $nd1
+" ...");
results.add($nto);
end
------------------------------------------
This is the rule version which delivers the expected result (without using $nd1):
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
$nto: TestObject( date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+
$nto.getDate1() +" ...");
results.add($nto);
end
------------------------------------------
If wished, I have a corresponding JUnit test case for this issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:02 p.m.
New subject: [JBoss JIRA] (JBRULES-2257) Wrong condition evaluation if the condition contains a variable assignment
[
https://issues.jboss.org/browse/JBRULES-2257?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-2257:
--------------------------------------
Fix Version/s: 5.4.0.Beta1
(was: 5.3.0.Final)
Wrong condition evaluation if the condition contains a variable
assignment
----------------------------------------------------------------------------
Key: JBRULES-2257
URL: https://issues.jboss.org/browse/JBRULES-2257
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core
Affects Versions: 5.0.1.FINAL
Environment: Mac OS X, iMac, Eclipse Galileo (3.5)
Reporter: Udo Klinkmüller
Assignee: Edson Tirelli
Fix For: 5.4.0.Beta1
I have a rule which checks variables of two equal objects in an old and a new version. If
I work with the variable daclaration $nd1 then the consequence is NOT executed although it
should.
This is the version of the rule in that the consequence is not executed although it
should:
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
TestObject( $nd1: date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+ $nd1
+" ...");
results.add($nto);
end
------------------------------------------
This is the rule version which delivers the expected result (without using $nd1):
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
$nto: TestObject( date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+
$nto.getDate1() +" ...");
results.add($nto);
end
------------------------------------------
If wished, I have a corresponding JUnit test case for this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:15 a.m.
New subject: [JBoss JIRA] (JBRULES-2257) Wrong condition evaluation if the condition contains a variable assignment
[
https://issues.jboss.org/browse/JBRULES-2257?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-2257:
--------------------------------------
Fix Version/s: 5.4.0.Beta2
(was: 5.4.0.Beta1)
Wrong condition evaluation if the condition contains a variable
assignment
----------------------------------------------------------------------------
Key: JBRULES-2257
URL: https://issues.jboss.org/browse/JBRULES-2257
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core
Affects Versions: 5.0.1.FINAL
Environment: Mac OS X, iMac, Eclipse Galileo (3.5)
Reporter: Udo Klinkmüller
Assignee: Edson Tirelli
Fix For: 5.4.0.Beta2
I have a rule which checks variables of two equal objects in an old and a new version. If
I work with the variable daclaration $nd1 then the consequence is NOT executed although it
should.
This is the version of the rule in that the consequence is not executed although it
should:
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
TestObject( $nd1: date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+ $nd1
+" ...");
results.add($nto);
end
------------------------------------------
This is the rule version which delivers the expected result (without using $nd1):
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
$nto: TestObject( date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+
$nto.getDate1() +" ...");
results.add($nto);
end
------------------------------------------
If wished, I have a corresponding JUnit test case for this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:26 a.m.
New subject: [JBoss JIRA] (JBRULES-2257) Wrong condition evaluation if the condition contains a variable assignment
[
https://issues.jboss.org/browse/JBRULES-2257?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-2257:
--------------------------------------
Fix Version/s: 5.4.0.Beta3
(was: 5.4.0.Beta2)
Wrong condition evaluation if the condition contains a variable
assignment
----------------------------------------------------------------------------
Key: JBRULES-2257
URL: https://issues.jboss.org/browse/JBRULES-2257
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core
Affects Versions: 5.0.1.FINAL
Environment: Mac OS X, iMac, Eclipse Galileo (3.5)
Reporter: Udo Klinkmüller
Assignee: Edson Tirelli
Fix For: 5.4.0.Beta3
I have a rule which checks variables of two equal objects in an old and a new version. If
I work with the variable daclaration $nd1 then the consequence is NOT executed although it
should.
This is the version of the rule in that the consequence is not executed although it
should:
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
TestObject( $nd1: date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+ $nd1
+" ...");
results.add($nto);
end
------------------------------------------
This is the rule version which delivers the expected result (without using $nd1):
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
$nto: TestObject( date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+
$nto.getDate1() +" ...");
results.add($nto);
end
------------------------------------------
If wished, I have a corresponding JUnit test case for this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:37 a.m.
New subject: [JBoss JIRA] (JBRULES-2257) Wrong condition evaluation if the condition contains a variable assignment
[
https://issues.jboss.org/browse/JBRULES-2257?page=com.atlassian.jira.plug...
]
Toni Rikkola updated JBRULES-2257:
----------------------------------
Fix Version/s: 5.4.0.Final
(was: 5.4.0.CR1)
Wrong condition evaluation if the condition contains a variable
assignment
----------------------------------------------------------------------------
Key: JBRULES-2257
URL: https://issues.jboss.org/browse/JBRULES-2257
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core
Affects Versions: 5.0.1.FINAL
Environment: Mac OS X, iMac, Eclipse Galileo (3.5)
Reporter: Udo Klinkmüller
Assignee: Edson Tirelli
Fix For: 5.4.0.Final
I have a rule which checks variables of two equal objects in an old and a new version. If
I work with the variable daclaration $nd1 then the consequence is NOT executed although it
should.
This is the version of the rule in that the consequence is not executed although it
should:
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
TestObject( $nd1: date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+ $nd1
+" ...");
results.add($nto);
end
------------------------------------------
This is the rule version which delivers the expected result (without using $nd1):
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
$nto: TestObject( date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+
$nto.getDate1() +" ...");
results.add($nto);
end
------------------------------------------
If wished, I have a corresponding JUnit test case for this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:01 p.m.
New subject: [JBoss JIRA] (JBRULES-2257) Wrong condition evaluation if the condition contains a variable assignment
[
https://issues.jboss.org/browse/JBRULES-2257?page=com.atlassian.jira.plug...
]
Toni Rikkola updated JBRULES-2257:
----------------------------------
Fix Version/s: 5.5.0.Beta1
(was: 5.4.0.Final)
Wrong condition evaluation if the condition contains a variable
assignment
----------------------------------------------------------------------------
Key: JBRULES-2257
URL: https://issues.jboss.org/browse/JBRULES-2257
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core
Affects Versions: 5.0.1.FINAL
Environment: Mac OS X, iMac, Eclipse Galileo (3.5)
Reporter: Udo Klinkmüller
Assignee: Edson Tirelli
Fix For: 5.5.0.Beta1
I have a rule which checks variables of two equal objects in an old and a new version. If
I work with the variable daclaration $nd1 then the consequence is NOT executed although it
should.
This is the version of the rule in that the consequence is not executed although it
should:
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
TestObject( $nd1: date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+ $nd1
+" ...");
results.add($nto);
end
------------------------------------------
This is the rule version which delivers the expected result (without using $nd1):
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
$nto: TestObject( date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+
$nto.getDate1() +" ...");
results.add($nto);
end
------------------------------------------
If wished, I have a corresponding JUnit test case for this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:29 a.m.
New subject: [JBoss JIRA] (JBRULES-2257) Wrong condition evaluation if the condition contains a variable assignment
[
https://issues.jboss.org/browse/JBRULES-2257?page=com.atlassian.jira.plug...
]
Michael Anstis updated JBRULES-2257:
------------------------------------
Fix Version/s: 5.5.0.CR1
(was: 5.5.0.Beta1)
Wrong condition evaluation if the condition contains a variable
assignment
----------------------------------------------------------------------------
Key: JBRULES-2257
URL: https://issues.jboss.org/browse/JBRULES-2257
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core
Affects Versions: 5.0.1.FINAL
Environment: Mac OS X, iMac, Eclipse Galileo (3.5)
Reporter: Udo Klinkmüller
Assignee: Edson Tirelli
Fix For: 5.5.0.CR1
I have a rule which checks variables of two equal objects in an old and a new version. If
I work with the variable daclaration $nd1 then the consequence is NOT executed although it
should.
This is the version of the rule in that the consequence is not executed although it
should:
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
TestObject( $nd1: date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+ $nd1
+" ...");
results.add($nto);
end
------------------------------------------
This is the rule version which delivers the expected result (without using $nd1):
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
$nto: TestObject( date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+
$nto.getDate1() +" ...");
results.add($nto);
end
------------------------------------------
If wished, I have a corresponding JUnit test case for this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:43 p.m.
New subject: [JBoss JIRA] (JBRULES-2257) Wrong condition evaluation if the condition contains a variable assignment
[
https://issues.jboss.org/browse/JBRULES-2257?page=com.atlassian.jira.plug...
]
Michael Anstis updated JBRULES-2257:
------------------------------------
Fix Version/s: 6.0.0.Beta1
(was: 5.5.0.CR1)
Wrong condition evaluation if the condition contains a variable
assignment
----------------------------------------------------------------------------
Key: JBRULES-2257
URL: https://issues.jboss.org/browse/JBRULES-2257
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core
Affects Versions: 5.0.1.FINAL
Environment: Mac OS X, iMac, Eclipse Galileo (3.5)
Reporter: Udo Klinkmüller
Assignee: Edson Tirelli
Fix For: 6.0.0.Beta1
I have a rule which checks variables of two equal objects in an old and a new version. If
I work with the variable daclaration $nd1 then the consequence is NOT executed although it
should.
This is the version of the rule in that the consequence is not executed although it
should:
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
TestObject( $nd1: date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+ $nd1
+" ...");
results.add($nto);
end
------------------------------------------
This is the rule version which delivers the expected result (without using $nd1):
------------------------------------------
package apm.event.resource;
#list any import classes here.
import java.util.*;
import de.fraport.test.*;
#declare any global variables here
global Collection results;
rule "Test-Del"
salience 900
when
#conditions
TestMainObjectPair( $omo: oldMainObject != null, $nmo: newMainObject )
TestObject( date1 == null, $od2: date2 != null, $os1: strVal1 != null ) from
$omo.testObject
$nto: TestObject( date1 != null || date2 != $od2 || strVal1 != $os1 ) from
$nmo.testObject
then
#actions
System.out.println("****** Executing consequence of rule Test-Del nd1="+
$nto.getDate1() +" ...");
results.add($nto);
end
------------------------------------------
If wished, I have a corresponding JUnit test case for this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4204
days inactive
5360
days old
20 comments
8 participants
participants (8)
-
Edson Tirelli (JIRA) -
Geoffrey De Smet (JIRA)
-
Geoffrey De Smet (Updated) (JIRA)
-
Mark Proctor (JIRA)
-
Michael Anstis (JIRA)
-
Michael Paitl (JIRA)
-
Toni Rikkola (JIRA)
-
Udo Klinkmüller (JIRA)