[JBoss JIRA] (JBRULES-3302) Unwanted type coersion of String to float values when using "in" keyword LHS
6:55 p.m.
Unwanted type coersion of String to float values when using "in" keyword LHS
----------------------------------------------------------------------------
Key: JBRULES-3302
URL: https://issues.jboss.org/browse/JBRULES-3302
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.3.0.Final, 5.2.0.Final
Environment: Windows 7, Rational Application Developer 7.5, Eclipse Helios
Service Release 2
Reporter: Troy Parrish
Assignee: Mark Proctor
String values get treated as float values even when fact declares the property as a String
when using the "in" keyword to evaluate a String value against a set of values
in the lhs of the rule.
Example:
input into session : "10.5"
will match against all of the following values "10.5", "10.50",
"10.500" etc when in this format:
when
Fact(string in ("11.5", "10.50", "11.500"))
then
This problem behavior occurs in 5.3.0Final, 5.2.0.Final but not in 5.1.0Final, this is
when Expert went from using mvel 2.0.16 to mvel 2.1.0
--
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
7:51 p.m.
[
https://issues.jboss.org/browse/JBRULES-3302?page=com.atlassian.jira.plug...
]
Troy Parrish updated JBRULES-3302:
----------------------------------
Description:
String values get treated as float values even when fact declares the property as a String
when using the "in" keyword to evaluate a String value against a set of values
in the lhs of the rule.
Example:
input into session : "10.5"
will match against all of the following values "10.5", "10.50",
"10.500" etc when in this format:
when
Fact(string in ("11.5", "10.50", "11.500"))
then
This problem behavior occurs in 5.3.0Final, 5.2.0.Final but not in 5.1.0Final, this is
when Expert went from using mvel 2.0.16 to mvel 2.1.0
Further information based on recent findings (12/02/2011)
When inserting a Fact with a Property that is an Object and the LHS references a property
of that object there is the unwanted type coercion even in 5.1.0Final
IE:
Class BigTest has two properties: Test and id. Test is an Object with a single property:
code.
If we reference in the LHS BigTest(test.code in (.....)) we get the unwanted coercion, but
when we reference BigTest(id in (.....)) the coercion does not occur. This is for
5.1.0Final. We find that the coercion takes place for both the syntax of BigTest(id in
(......)) and BigTest(test.code in (.....)) when using 5.2.0Final and up. Example code
below:
CLASSES:
public class BigTest {
private Test test;
private String id;
getters and setters .....
public class Test {
private String code;
getters and setters .....
DRL:
rule "Test.Code One"
when
BigTest($code : test.code in ("1.50", "2.50"))
then
System.out.println("Code compared values: 1.50, 2.50 - actual code value:
" + $code);
end
rule "Test.Code Two"
when
BigTest($code : test.code in ("1.5", "2.5"))
then
System.out.println("Code compared values: 1.5, 2.5 - actual code value:
" + $code);
end
rule "Big Test ID One"
when
BigTest($id : id in ("3.5", "4.5"))
then
System.out.println("ID compared values: 3.5, 4.5 - actual ID value: " + $id);
end
rule "Big Test ID Two"
when
BigTest($id : id in ( "3.0", "4.0"))
then
System.out.println("ID compared values: 3.0, 4.0 - actual ID value: " + $id);
end
was:
String values get treated as float values even when fact declares the property as a String
when using the "in" keyword to evaluate a String value against a set of values
in the lhs of the rule.
Example:
input into session : "10.5"
will match against all of the following values "10.5", "10.50",
"10.500" etc when in this format:
when
Fact(string in ("11.5", "10.50", "11.500"))
then
This problem behavior occurs in 5.3.0Final, 5.2.0.Final but not in 5.1.0Final, this is
when Expert went from using mvel 2.0.16 to mvel 2.1.0
Forum Reference:
http://drools.46999.n3.nabble.com/Inadvertant-type-conversion-while-using...
(was:
http://drools.46999.n3.nabble.com/Inadvertant-type-conversion-while-using...)
Unwanted type coersion of String to float values when using
"in" keyword LHS
----------------------------------------------------------------------------
Key: JBRULES-3302
URL: https://issues.jboss.org/browse/JBRULES-3302
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.Final, 5.3.0.Final
Environment: Windows 7, Rational Application Developer 7.5, Eclipse Helios
Service Release 2
Reporter: Troy Parrish
Assignee: Mark Proctor
String values get treated as float values even when fact declares the property as a
String when using the "in" keyword to evaluate a String value against a set of
values in the lhs of the rule.
Example:
input into session : "10.5"
will match against all of the following values "10.5", "10.50",
"10.500" etc when in this format:
when
Fact(string in ("11.5", "10.50", "11.500"))
then
This problem behavior occurs in 5.3.0Final, 5.2.0.Final but not in 5.1.0Final, this is
when Expert went from using mvel 2.0.16 to mvel 2.1.0
Further information based on recent findings (12/02/2011)
When inserting a Fact with a Property that is an Object and the LHS references a property
of that object there is the unwanted type coercion even in 5.1.0Final
IE:
Class BigTest has two properties: Test and id. Test is an Object with a single property:
code.
If we reference in the LHS BigTest(test.code in (.....)) we get the unwanted coercion,
but when we reference BigTest(id in (.....)) the coercion does not occur. This is for
5.1.0Final. We find that the coercion takes place for both the syntax of BigTest(id in
(......)) and BigTest(test.code in (.....)) when using 5.2.0Final and up. Example code
below:
CLASSES:
public class BigTest {
private Test test;
private String id;
getters and setters .....
public class Test {
private String code;
getters and setters .....
DRL:
rule "Test.Code One"
when
BigTest($code : test.code in ("1.50", "2.50"))
then
System.out.println("Code compared values: 1.50, 2.50 - actual code value:
" + $code);
end
rule "Test.Code Two"
when
BigTest($code : test.code in ("1.5", "2.5"))
then
System.out.println("Code compared values: 1.5, 2.5 - actual code value:
" + $code);
end
rule "Big Test ID One"
when
BigTest($id : id in ("3.5", "4.5"))
then
System.out.println("ID compared values: 3.5, 4.5 - actual ID value: " +
$id);
end
rule "Big Test ID Two"
when
BigTest($id : id in ( "3.0", "4.0"))
then
System.out.println("ID compared values: 3.0, 4.0 - actual ID value: " +
$id);
end
--
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
3:36 p.m.
[
https://issues.jboss.org/browse/JBRULES-3302?page=com.atlassian.jira.plug...
]
Alessandro Lazarotti reassigned JBRULES-3302:
---------------------------------------------
Assignee: Mario Fusco (was: Mark Proctor)
Assign to Marco, according with talk by IRC
Unwanted type coersion of String to float values when using
"in" keyword LHS
----------------------------------------------------------------------------
Key: JBRULES-3302
URL: https://issues.jboss.org/browse/JBRULES-3302
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.Final, 5.3.0.Final
Environment: Windows 7, Rational Application Developer 7.5, Eclipse Helios
Service Release 2
Reporter: Troy Parrish
Assignee: Mario Fusco
String values get treated as float values even when fact declares the property as a
String when using the "in" keyword to evaluate a String value against a set of
values in the lhs of the rule.
Example:
input into session : "10.5"
will match against all of the following values "10.5", "10.50",
"10.500" etc when in this format:
when
Fact(string in ("11.5", "10.50", "11.500"))
then
This problem behavior occurs in 5.3.0Final, 5.2.0.Final but not in 5.1.0Final, this is
when Expert went from using mvel 2.0.16 to mvel 2.1.0
Further information based on recent findings (12/02/2011)
When inserting a Fact with a Property that is an Object and the LHS references a property
of that object there is the unwanted type coercion even in 5.1.0Final
IE:
Class BigTest has two properties: Test and id. Test is an Object with a single property:
code.
If we reference in the LHS BigTest(test.code in (.....)) we get the unwanted coercion,
but when we reference BigTest(id in (.....)) the coercion does not occur. This is for
5.1.0Final. We find that the coercion takes place for both the syntax of BigTest(id in
(......)) and BigTest(test.code in (.....)) when using 5.2.0Final and up. Example code
below:
CLASSES:
public class BigTest {
private Test test;
private String id;
getters and setters .....
public class Test {
private String code;
getters and setters .....
DRL:
rule "Test.Code One"
when
BigTest($code : test.code in ("1.50", "2.50"))
then
System.out.println("Code compared values: 1.50, 2.50 - actual code value:
" + $code);
end
rule "Test.Code Two"
when
BigTest($code : test.code in ("1.5", "2.5"))
then
System.out.println("Code compared values: 1.5, 2.5 - actual code value:
" + $code);
end
rule "Big Test ID One"
when
BigTest($id : id in ("3.5", "4.5"))
then
System.out.println("ID compared values: 3.5, 4.5 - actual ID value: " +
$id);
end
rule "Big Test ID Two"
when
BigTest($id : id in ( "3.0", "4.0"))
then
System.out.println("ID compared values: 3.0, 4.0 - actual ID value: " +
$id);
end
--
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:17 p.m.
[
https://issues.jboss.org/browse/JBRULES-3302?page=com.atlassian.jira.plug...
]
Alessandro Lazarotti edited comment on JBRULES-3302 at 1/13/12 3:17 PM:
------------------------------------------------------------------------
Assign to Mario, according with talk by IRC
was (Author: alessandrolt):
Assign to Marco, according with talk by IRC
Unwanted type coersion of String to float values when using
"in" keyword LHS
----------------------------------------------------------------------------
Key: JBRULES-3302
URL: https://issues.jboss.org/browse/JBRULES-3302
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.Final, 5.3.0.Final
Environment: Windows 7, Rational Application Developer 7.5, Eclipse Helios
Service Release 2
Reporter: Troy Parrish
Assignee: Mario Fusco
String values get treated as float values even when fact declares the property as a
String when using the "in" keyword to evaluate a String value against a set of
values in the lhs of the rule.
Example:
input into session : "10.5"
will match against all of the following values "10.5", "10.50",
"10.500" etc when in this format:
when
Fact(string in ("11.5", "10.50", "11.500"))
then
This problem behavior occurs in 5.3.0Final, 5.2.0.Final but not in 5.1.0Final, this is
when Expert went from using mvel 2.0.16 to mvel 2.1.0
Further information based on recent findings (12/02/2011)
When inserting a Fact with a Property that is an Object and the LHS references a property
of that object there is the unwanted type coercion even in 5.1.0Final
IE:
Class BigTest has two properties: Test and id. Test is an Object with a single property:
code.
If we reference in the LHS BigTest(test.code in (.....)) we get the unwanted coercion,
but when we reference BigTest(id in (.....)) the coercion does not occur. This is for
5.1.0Final. We find that the coercion takes place for both the syntax of BigTest(id in
(......)) and BigTest(test.code in (.....)) when using 5.2.0Final and up. Example code
below:
CLASSES:
public class BigTest {
private Test test;
private String id;
getters and setters .....
public class Test {
private String code;
getters and setters .....
DRL:
rule "Test.Code One"
when
BigTest($code : test.code in ("1.50", "2.50"))
then
System.out.println("Code compared values: 1.50, 2.50 - actual code value:
" + $code);
end
rule "Test.Code Two"
when
BigTest($code : test.code in ("1.5", "2.5"))
then
System.out.println("Code compared values: 1.5, 2.5 - actual code value:
" + $code);
end
rule "Big Test ID One"
when
BigTest($id : id in ("3.5", "4.5"))
then
System.out.println("ID compared values: 3.5, 4.5 - actual ID value: " +
$id);
end
rule "Big Test ID Two"
when
BigTest($id : id in ( "3.0", "4.0"))
then
System.out.println("ID compared values: 3.0, 4.0 - actual ID value: " +
$id);
end
--
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:22 p.m.
[
https://issues.jboss.org/browse/JBRULES-3302?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration updated JBRULES-3302:
---------------------------------------------
Bugzilla Update: Perform
Forum Reference:
http://drools.46999.n3.nabble.com/Inadvertant-type-conversion-while-using...
(was:
http://drools.46999.n3.nabble.com/Inadvertant-type-conversion-while-using...)
Unwanted type coersion of String to float values when using
"in" keyword LHS
----------------------------------------------------------------------------
Key: JBRULES-3302
URL: https://issues.jboss.org/browse/JBRULES-3302
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.Final, 5.3.0.Final
Environment: Windows 7, Rational Application Developer 7.5, Eclipse Helios
Service Release 2
Reporter: Troy Parrish
Assignee: Mario Fusco
String values get treated as float values even when fact declares the property as a
String when using the "in" keyword to evaluate a String value against a set of
values in the lhs of the rule.
Example:
input into session : "10.5"
will match against all of the following values "10.5", "10.50",
"10.500" etc when in this format:
when
Fact(string in ("11.5", "10.50", "11.500"))
then
This problem behavior occurs in 5.3.0Final, 5.2.0.Final but not in 5.1.0Final, this is
when Expert went from using mvel 2.0.16 to mvel 2.1.0
Further information based on recent findings (12/02/2011)
When inserting a Fact with a Property that is an Object and the LHS references a property
of that object there is the unwanted type coercion even in 5.1.0Final
IE:
Class BigTest has two properties: Test and id. Test is an Object with a single property:
code.
If we reference in the LHS BigTest(test.code in (.....)) we get the unwanted coercion,
but when we reference BigTest(id in (.....)) the coercion does not occur. This is for
5.1.0Final. We find that the coercion takes place for both the syntax of BigTest(id in
(......)) and BigTest(test.code in (.....)) when using 5.2.0Final and up. Example code
below:
CLASSES:
public class BigTest {
private Test test;
private String id;
getters and setters .....
public class Test {
private String code;
getters and setters .....
DRL:
rule "Test.Code One"
when
BigTest($code : test.code in ("1.50", "2.50"))
then
System.out.println("Code compared values: 1.50, 2.50 - actual code value:
" + $code);
end
rule "Test.Code Two"
when
BigTest($code : test.code in ("1.5", "2.5"))
then
System.out.println("Code compared values: 1.5, 2.5 - actual code value:
" + $code);
end
rule "Big Test ID One"
when
BigTest($id : id in ("3.5", "4.5"))
then
System.out.println("ID compared values: 3.5, 4.5 - actual ID value: " +
$id);
end
rule "Big Test ID Two"
when
BigTest($id : id in ( "3.0", "4.0"))
then
System.out.println("ID compared values: 3.0, 4.0 - actual ID value: " +
$id);
end
--
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:22 p.m.
[
https://issues.jboss.org/browse/JBRULES-3302?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration updated JBRULES-3302:
---------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=768952
Forum Reference:
http://drools.46999.n3.nabble.com/Inadvertant-type-conversion-while-using...
(was:
http://drools.46999.n3.nabble.com/Inadvertant-type-conversion-while-using...)
Unwanted type coersion of String to float values when using
"in" keyword LHS
----------------------------------------------------------------------------
Key: JBRULES-3302
URL: https://issues.jboss.org/browse/JBRULES-3302
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.Final, 5.3.0.Final
Environment: Windows 7, Rational Application Developer 7.5, Eclipse Helios
Service Release 2
Reporter: Troy Parrish
Assignee: Mario Fusco
String values get treated as float values even when fact declares the property as a
String when using the "in" keyword to evaluate a String value against a set of
values in the lhs of the rule.
Example:
input into session : "10.5"
will match against all of the following values "10.5", "10.50",
"10.500" etc when in this format:
when
Fact(string in ("11.5", "10.50", "11.500"))
then
This problem behavior occurs in 5.3.0Final, 5.2.0.Final but not in 5.1.0Final, this is
when Expert went from using mvel 2.0.16 to mvel 2.1.0
Further information based on recent findings (12/02/2011)
When inserting a Fact with a Property that is an Object and the LHS references a property
of that object there is the unwanted type coercion even in 5.1.0Final
IE:
Class BigTest has two properties: Test and id. Test is an Object with a single property:
code.
If we reference in the LHS BigTest(test.code in (.....)) we get the unwanted coercion,
but when we reference BigTest(id in (.....)) the coercion does not occur. This is for
5.1.0Final. We find that the coercion takes place for both the syntax of BigTest(id in
(......)) and BigTest(test.code in (.....)) when using 5.2.0Final and up. Example code
below:
CLASSES:
public class BigTest {
private Test test;
private String id;
getters and setters .....
public class Test {
private String code;
getters and setters .....
DRL:
rule "Test.Code One"
when
BigTest($code : test.code in ("1.50", "2.50"))
then
System.out.println("Code compared values: 1.50, 2.50 - actual code value:
" + $code);
end
rule "Test.Code Two"
when
BigTest($code : test.code in ("1.5", "2.5"))
then
System.out.println("Code compared values: 1.5, 2.5 - actual code value:
" + $code);
end
rule "Big Test ID One"
when
BigTest($id : id in ("3.5", "4.5"))
then
System.out.println("ID compared values: 3.5, 4.5 - actual ID value: " +
$id);
end
rule "Big Test ID Two"
when
BigTest($id : id in ( "3.0", "4.0"))
then
System.out.println("ID compared values: 3.0, 4.0 - actual ID value: " +
$id);
end
--
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:53 p.m.
[
https://issues.jboss.org/browse/JBRULES-3302?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration commented on JBRULES-3302:
--------------------------------------------------
JBoss Product and Program Management <pm-jboss(a)redhat.com> made a private comment on
[bug 768952|https://bugzilla.redhat.com/show_bug.cgi?id=768952]
Unwanted type coersion of String to float values when using
"in" keyword LHS
----------------------------------------------------------------------------
Key: JBRULES-3302
URL: https://issues.jboss.org/browse/JBRULES-3302
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.Final, 5.3.0.Final
Environment: Windows 7, Rational Application Developer 7.5, Eclipse Helios
Service Release 2
Reporter: Troy Parrish
Assignee: Mario Fusco
String values get treated as float values even when fact declares the property as a
String when using the "in" keyword to evaluate a String value against a set of
values in the lhs of the rule.
Example:
input into session : "10.5"
will match against all of the following values "10.5", "10.50",
"10.500" etc when in this format:
when
Fact(string in ("11.5", "10.50", "11.500"))
then
This problem behavior occurs in 5.3.0Final, 5.2.0.Final but not in 5.1.0Final, this is
when Expert went from using mvel 2.0.16 to mvel 2.1.0
Further information based on recent findings (12/02/2011)
When inserting a Fact with a Property that is an Object and the LHS references a property
of that object there is the unwanted type coercion even in 5.1.0Final
IE:
Class BigTest has two properties: Test and id. Test is an Object with a single property:
code.
If we reference in the LHS BigTest(test.code in (.....)) we get the unwanted coercion,
but when we reference BigTest(id in (.....)) the coercion does not occur. This is for
5.1.0Final. We find that the coercion takes place for both the syntax of BigTest(id in
(......)) and BigTest(test.code in (.....)) when using 5.2.0Final and up. Example code
below:
CLASSES:
public class BigTest {
private Test test;
private String id;
getters and setters .....
public class Test {
private String code;
getters and setters .....
DRL:
rule "Test.Code One"
when
BigTest($code : test.code in ("1.50", "2.50"))
then
System.out.println("Code compared values: 1.50, 2.50 - actual code value:
" + $code);
end
rule "Test.Code Two"
when
BigTest($code : test.code in ("1.5", "2.5"))
then
System.out.println("Code compared values: 1.5, 2.5 - actual code value:
" + $code);
end
rule "Big Test ID One"
when
BigTest($id : id in ("3.5", "4.5"))
then
System.out.println("ID compared values: 3.5, 4.5 - actual ID value: " +
$id);
end
rule "Big Test ID Two"
when
BigTest($id : id in ( "3.0", "4.0"))
then
System.out.println("ID compared values: 3.0, 4.0 - actual ID value: " +
$id);
end
--
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:02 a.m.
[
https://issues.jboss.org/browse/JBRULES-3302?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration commented on JBRULES-3302:
--------------------------------------------------
Mark Proctor <mproctor(a)redhat.com> changed the Status of [bug
768952|https://bugzilla.redhat.com/show_bug.cgi?id=768952] from NEW to ASSIGNED
Unwanted type coersion of String to float values when using
"in" keyword LHS
----------------------------------------------------------------------------
Key: JBRULES-3302
URL: https://issues.jboss.org/browse/JBRULES-3302
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.Final, 5.3.0.Final
Environment: Windows 7, Rational Application Developer 7.5, Eclipse Helios
Service Release 2
Reporter: Troy Parrish
Assignee: Mario Fusco
String values get treated as float values even when fact declares the property as a
String when using the "in" keyword to evaluate a String value against a set of
values in the lhs of the rule.
Example:
input into session : "10.5"
will match against all of the following values "10.5", "10.50",
"10.500" etc when in this format:
when
Fact(string in ("11.5", "10.50", "11.500"))
then
This problem behavior occurs in 5.3.0Final, 5.2.0.Final but not in 5.1.0Final, this is
when Expert went from using mvel 2.0.16 to mvel 2.1.0
Further information based on recent findings (12/02/2011)
When inserting a Fact with a Property that is an Object and the LHS references a property
of that object there is the unwanted type coercion even in 5.1.0Final
IE:
Class BigTest has two properties: Test and id. Test is an Object with a single property:
code.
If we reference in the LHS BigTest(test.code in (.....)) we get the unwanted coercion,
but when we reference BigTest(id in (.....)) the coercion does not occur. This is for
5.1.0Final. We find that the coercion takes place for both the syntax of BigTest(id in
(......)) and BigTest(test.code in (.....)) when using 5.2.0Final and up. Example code
below:
CLASSES:
public class BigTest {
private Test test;
private String id;
getters and setters .....
public class Test {
private String code;
getters and setters .....
DRL:
rule "Test.Code One"
when
BigTest($code : test.code in ("1.50", "2.50"))
then
System.out.println("Code compared values: 1.50, 2.50 - actual code value:
" + $code);
end
rule "Test.Code Two"
when
BigTest($code : test.code in ("1.5", "2.5"))
then
System.out.println("Code compared values: 1.5, 2.5 - actual code value:
" + $code);
end
rule "Big Test ID One"
when
BigTest($id : id in ("3.5", "4.5"))
then
System.out.println("ID compared values: 3.5, 4.5 - actual ID value: " +
$id);
end
rule "Big Test ID Two"
when
BigTest($id : id in ( "3.0", "4.0"))
then
System.out.println("ID compared values: 3.0, 4.0 - actual ID value: " +
$id);
end
--
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:36 a.m.
[
https://issues.jboss.org/browse/JBRULES-3302?page=com.atlassian.jira.plug...
]
Mario Fusco resolved JBRULES-3302.
----------------------------------
Fix Version/s: 5.4.0.Beta2
Resolution: Done
That was caused by a wrong type coersion in mvel
Unwanted type coersion of String to float values when using
"in" keyword LHS
----------------------------------------------------------------------------
Key: JBRULES-3302
URL: https://issues.jboss.org/browse/JBRULES-3302
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.Final, 5.3.0.Final
Environment: Windows 7, Rational Application Developer 7.5, Eclipse Helios
Service Release 2
Reporter: Troy Parrish
Assignee: Mario Fusco
Fix For: 5.4.0.Beta2
String values get treated as float values even when fact declares the property as a
String when using the "in" keyword to evaluate a String value against a set of
values in the lhs of the rule.
Example:
input into session : "10.5"
will match against all of the following values "10.5", "10.50",
"10.500" etc when in this format:
when
Fact(string in ("11.5", "10.50", "11.500"))
then
This problem behavior occurs in 5.3.0Final, 5.2.0.Final but not in 5.1.0Final, this is
when Expert went from using mvel 2.0.16 to mvel 2.1.0
Further information based on recent findings (12/02/2011)
When inserting a Fact with a Property that is an Object and the LHS references a property
of that object there is the unwanted type coercion even in 5.1.0Final
IE:
Class BigTest has two properties: Test and id. Test is an Object with a single property:
code.
If we reference in the LHS BigTest(test.code in (.....)) we get the unwanted coercion,
but when we reference BigTest(id in (.....)) the coercion does not occur. This is for
5.1.0Final. We find that the coercion takes place for both the syntax of BigTest(id in
(......)) and BigTest(test.code in (.....)) when using 5.2.0Final and up. Example code
below:
CLASSES:
public class BigTest {
private Test test;
private String id;
getters and setters .....
public class Test {
private String code;
getters and setters .....
DRL:
rule "Test.Code One"
when
BigTest($code : test.code in ("1.50", "2.50"))
then
System.out.println("Code compared values: 1.50, 2.50 - actual code value:
" + $code);
end
rule "Test.Code Two"
when
BigTest($code : test.code in ("1.5", "2.5"))
then
System.out.println("Code compared values: 1.5, 2.5 - actual code value:
" + $code);
end
rule "Big Test ID One"
when
BigTest($id : id in ("3.5", "4.5"))
then
System.out.println("ID compared values: 3.5, 4.5 - actual ID value: " +
$id);
end
rule "Big Test ID Two"
when
BigTest($id : id in ( "3.0", "4.0"))
then
System.out.println("ID compared values: 3.0, 4.0 - actual ID value: " +
$id);
end
--
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
5:39 p.m.
[
https://issues.jboss.org/browse/JBRULES-3302?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration commented on JBRULES-3302:
--------------------------------------------------
Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug
768952|https://bugzilla.redhat.com/show_bug.cgi?id=768952] from ASSIGNED to MODIFIED
Unwanted type coersion of String to float values when using
"in" keyword LHS
----------------------------------------------------------------------------
Key: JBRULES-3302
URL: https://issues.jboss.org/browse/JBRULES-3302
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.Final, 5.3.0.Final
Environment: Windows 7, Rational Application Developer 7.5, Eclipse Helios
Service Release 2
Reporter: Troy Parrish
Assignee: Mario Fusco
Fix For: 5.4.0.Beta2
String values get treated as float values even when fact declares the property as a
String when using the "in" keyword to evaluate a String value against a set of
values in the lhs of the rule.
Example:
input into session : "10.5"
will match against all of the following values "10.5", "10.50",
"10.500" etc when in this format:
when
Fact(string in ("11.5", "10.50", "11.500"))
then
This problem behavior occurs in 5.3.0Final, 5.2.0.Final but not in 5.1.0Final, this is
when Expert went from using mvel 2.0.16 to mvel 2.1.0
Further information based on recent findings (12/02/2011)
When inserting a Fact with a Property that is an Object and the LHS references a property
of that object there is the unwanted type coercion even in 5.1.0Final
IE:
Class BigTest has two properties: Test and id. Test is an Object with a single property:
code.
If we reference in the LHS BigTest(test.code in (.....)) we get the unwanted coercion,
but when we reference BigTest(id in (.....)) the coercion does not occur. This is for
5.1.0Final. We find that the coercion takes place for both the syntax of BigTest(id in
(......)) and BigTest(test.code in (.....)) when using 5.2.0Final and up. Example code
below:
CLASSES:
public class BigTest {
private Test test;
private String id;
getters and setters .....
public class Test {
private String code;
getters and setters .....
DRL:
rule "Test.Code One"
when
BigTest($code : test.code in ("1.50", "2.50"))
then
System.out.println("Code compared values: 1.50, 2.50 - actual code value:
" + $code);
end
rule "Test.Code Two"
when
BigTest($code : test.code in ("1.5", "2.5"))
then
System.out.println("Code compared values: 1.5, 2.5 - actual code value:
" + $code);
end
rule "Big Test ID One"
when
BigTest($id : id in ("3.5", "4.5"))
then
System.out.println("ID compared values: 3.5, 4.5 - actual ID value: " +
$id);
end
rule "Big Test ID Two"
when
BigTest($id : id in ( "3.0", "4.0"))
then
System.out.println("ID compared values: 3.0, 4.0 - actual ID value: " +
$id);
end
--
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
5:39 p.m.
[
https://issues.jboss.org/browse/JBRULES-3302?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration commented on JBRULES-3302:
--------------------------------------------------
JBoss JIRA Server <jira-update(a)redhat.com> made a comment on [bug
768952|https://bugzilla.redhat.com/show_bug.cgi?id=768952]
Mario Fusco <mario.fusco(a)gmail.com> made a comment on jira JBRULES-3302
That was caused by a wrong type coersion in mvel
Unwanted type coersion of String to float values when using
"in" keyword LHS
----------------------------------------------------------------------------
Key: JBRULES-3302
URL: https://issues.jboss.org/browse/JBRULES-3302
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.Final, 5.3.0.Final
Environment: Windows 7, Rational Application Developer 7.5, Eclipse Helios
Service Release 2
Reporter: Troy Parrish
Assignee: Mario Fusco
Fix For: 5.4.0.Beta2
String values get treated as float values even when fact declares the property as a
String when using the "in" keyword to evaluate a String value against a set of
values in the lhs of the rule.
Example:
input into session : "10.5"
will match against all of the following values "10.5", "10.50",
"10.500" etc when in this format:
when
Fact(string in ("11.5", "10.50", "11.500"))
then
This problem behavior occurs in 5.3.0Final, 5.2.0.Final but not in 5.1.0Final, this is
when Expert went from using mvel 2.0.16 to mvel 2.1.0
Further information based on recent findings (12/02/2011)
When inserting a Fact with a Property that is an Object and the LHS references a property
of that object there is the unwanted type coercion even in 5.1.0Final
IE:
Class BigTest has two properties: Test and id. Test is an Object with a single property:
code.
If we reference in the LHS BigTest(test.code in (.....)) we get the unwanted coercion,
but when we reference BigTest(id in (.....)) the coercion does not occur. This is for
5.1.0Final. We find that the coercion takes place for both the syntax of BigTest(id in
(......)) and BigTest(test.code in (.....)) when using 5.2.0Final and up. Example code
below:
CLASSES:
public class BigTest {
private Test test;
private String id;
getters and setters .....
public class Test {
private String code;
getters and setters .....
DRL:
rule "Test.Code One"
when
BigTest($code : test.code in ("1.50", "2.50"))
then
System.out.println("Code compared values: 1.50, 2.50 - actual code value:
" + $code);
end
rule "Test.Code Two"
when
BigTest($code : test.code in ("1.5", "2.5"))
then
System.out.println("Code compared values: 1.5, 2.5 - actual code value:
" + $code);
end
rule "Big Test ID One"
when
BigTest($id : id in ("3.5", "4.5"))
then
System.out.println("ID compared values: 3.5, 4.5 - actual ID value: " +
$id);
end
rule "Big Test ID Two"
when
BigTest($id : id in ( "3.0", "4.0"))
then
System.out.println("ID compared values: 3.0, 4.0 - actual ID value: " +
$id);
end
--
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
5:39 p.m.
[
https://issues.jboss.org/browse/JBRULES-3302?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration commented on JBRULES-3302:
--------------------------------------------------
JBoss JIRA Server <jira-update(a)redhat.com> made a comment on [bug
768952|https://bugzilla.redhat.com/show_bug.cgi?id=768952]
Mario Fusco <mario.fusco(a)gmail.com> updated the status of jira JBRULES-3302 to
Resolved
Unwanted type coersion of String to float values when using
"in" keyword LHS
----------------------------------------------------------------------------
Key: JBRULES-3302
URL: https://issues.jboss.org/browse/JBRULES-3302
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.Final, 5.3.0.Final
Environment: Windows 7, Rational Application Developer 7.5, Eclipse Helios
Service Release 2
Reporter: Troy Parrish
Assignee: Mario Fusco
Fix For: 5.4.0.Beta2
String values get treated as float values even when fact declares the property as a
String when using the "in" keyword to evaluate a String value against a set of
values in the lhs of the rule.
Example:
input into session : "10.5"
will match against all of the following values "10.5", "10.50",
"10.500" etc when in this format:
when
Fact(string in ("11.5", "10.50", "11.500"))
then
This problem behavior occurs in 5.3.0Final, 5.2.0.Final but not in 5.1.0Final, this is
when Expert went from using mvel 2.0.16 to mvel 2.1.0
Further information based on recent findings (12/02/2011)
When inserting a Fact with a Property that is an Object and the LHS references a property
of that object there is the unwanted type coercion even in 5.1.0Final
IE:
Class BigTest has two properties: Test and id. Test is an Object with a single property:
code.
If we reference in the LHS BigTest(test.code in (.....)) we get the unwanted coercion,
but when we reference BigTest(id in (.....)) the coercion does not occur. This is for
5.1.0Final. We find that the coercion takes place for both the syntax of BigTest(id in
(......)) and BigTest(test.code in (.....)) when using 5.2.0Final and up. Example code
below:
CLASSES:
public class BigTest {
private Test test;
private String id;
getters and setters .....
public class Test {
private String code;
getters and setters .....
DRL:
rule "Test.Code One"
when
BigTest($code : test.code in ("1.50", "2.50"))
then
System.out.println("Code compared values: 1.50, 2.50 - actual code value:
" + $code);
end
rule "Test.Code Two"
when
BigTest($code : test.code in ("1.5", "2.5"))
then
System.out.println("Code compared values: 1.5, 2.5 - actual code value:
" + $code);
end
rule "Big Test ID One"
when
BigTest($id : id in ("3.5", "4.5"))
then
System.out.println("ID compared values: 3.5, 4.5 - actual ID value: " +
$id);
end
rule "Big Test ID Two"
when
BigTest($id : id in ( "3.0", "4.0"))
then
System.out.println("ID compared values: 3.0, 4.0 - actual ID value: " +
$id);
end
--
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:13 p.m.
[
https://issues.jboss.org/browse/JBRULES-3302?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration commented on JBRULES-3302:
--------------------------------------------------
JBoss Product and Program Management <pm-jboss(a)redhat.com> made a private comment on
[bug 768952|https://bugzilla.redhat.com/show_bug.cgi?id=768952]
Unwanted type coersion of String to float values when using
"in" keyword LHS
----------------------------------------------------------------------------
Key: JBRULES-3302
URL: https://issues.jboss.org/browse/JBRULES-3302
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.Final, 5.3.0.Final
Environment: Windows 7, Rational Application Developer 7.5, Eclipse Helios
Service Release 2
Reporter: Troy Parrish
Assignee: Mario Fusco
Fix For: 5.4.0.Beta2
String values get treated as float values even when fact declares the property as a
String when using the "in" keyword to evaluate a String value against a set of
values in the lhs of the rule.
Example:
input into session : "10.5"
will match against all of the following values "10.5", "10.50",
"10.500" etc when in this format:
when
Fact(string in ("11.5", "10.50", "11.500"))
then
This problem behavior occurs in 5.3.0Final, 5.2.0.Final but not in 5.1.0Final, this is
when Expert went from using mvel 2.0.16 to mvel 2.1.0
Further information based on recent findings (12/02/2011)
When inserting a Fact with a Property that is an Object and the LHS references a property
of that object there is the unwanted type coercion even in 5.1.0Final
IE:
Class BigTest has two properties: Test and id. Test is an Object with a single property:
code.
If we reference in the LHS BigTest(test.code in (.....)) we get the unwanted coercion,
but when we reference BigTest(id in (.....)) the coercion does not occur. This is for
5.1.0Final. We find that the coercion takes place for both the syntax of BigTest(id in
(......)) and BigTest(test.code in (.....)) when using 5.2.0Final and up. Example code
below:
CLASSES:
public class BigTest {
private Test test;
private String id;
getters and setters .....
public class Test {
private String code;
getters and setters .....
DRL:
rule "Test.Code One"
when
BigTest($code : test.code in ("1.50", "2.50"))
then
System.out.println("Code compared values: 1.50, 2.50 - actual code value:
" + $code);
end
rule "Test.Code Two"
when
BigTest($code : test.code in ("1.5", "2.5"))
then
System.out.println("Code compared values: 1.5, 2.5 - actual code value:
" + $code);
end
rule "Big Test ID One"
when
BigTest($id : id in ("3.5", "4.5"))
then
System.out.println("ID compared values: 3.5, 4.5 - actual ID value: " +
$id);
end
rule "Big Test ID Two"
when
BigTest($id : id in ( "3.0", "4.0"))
then
System.out.println("ID compared values: 3.0, 4.0 - actual ID value: " +
$id);
end
--
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
10:14 a.m.
[
https://issues.jboss.org/browse/JBRULES-3302?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration commented on JBRULES-3302:
--------------------------------------------------
Ryan Zhang <rzhang(a)redhat.com> made a comment on [bug
768952|https://bugzilla.redhat.com/show_bug.cgi?id=768952]
Please verify the issue on 5.3 ER4.
Unwanted type coersion of String to float values when using
"in" keyword LHS
----------------------------------------------------------------------------
Key: JBRULES-3302
URL: https://issues.jboss.org/browse/JBRULES-3302
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.Final, 5.3.0.Final
Environment: Windows 7, Rational Application Developer 7.5, Eclipse Helios
Service Release 2
Reporter: Troy Parrish
Assignee: Mario Fusco
Fix For: 5.4.0.Beta2
String values get treated as float values even when fact declares the property as a
String when using the "in" keyword to evaluate a String value against a set of
values in the lhs of the rule.
Example:
input into session : "10.5"
will match against all of the following values "10.5", "10.50",
"10.500" etc when in this format:
when
Fact(string in ("11.5", "10.50", "11.500"))
then
This problem behavior occurs in 5.3.0Final, 5.2.0.Final but not in 5.1.0Final, this is
when Expert went from using mvel 2.0.16 to mvel 2.1.0
Further information based on recent findings (12/02/2011)
When inserting a Fact with a Property that is an Object and the LHS references a property
of that object there is the unwanted type coercion even in 5.1.0Final
IE:
Class BigTest has two properties: Test and id. Test is an Object with a single property:
code.
If we reference in the LHS BigTest(test.code in (.....)) we get the unwanted coercion,
but when we reference BigTest(id in (.....)) the coercion does not occur. This is for
5.1.0Final. We find that the coercion takes place for both the syntax of BigTest(id in
(......)) and BigTest(test.code in (.....)) when using 5.2.0Final and up. Example code
below:
CLASSES:
public class BigTest {
private Test test;
private String id;
getters and setters .....
public class Test {
private String code;
getters and setters .....
DRL:
rule "Test.Code One"
when
BigTest($code : test.code in ("1.50", "2.50"))
then
System.out.println("Code compared values: 1.50, 2.50 - actual code value:
" + $code);
end
rule "Test.Code Two"
when
BigTest($code : test.code in ("1.5", "2.5"))
then
System.out.println("Code compared values: 1.5, 2.5 - actual code value:
" + $code);
end
rule "Big Test ID One"
when
BigTest($id : id in ("3.5", "4.5"))
then
System.out.println("ID compared values: 3.5, 4.5 - actual ID value: " +
$id);
end
rule "Big Test ID Two"
when
BigTest($id : id in ( "3.0", "4.0"))
then
System.out.println("ID compared values: 3.0, 4.0 - actual ID value: " +
$id);
end
--
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
10:14 a.m.
[
https://issues.jboss.org/browse/JBRULES-3302?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration commented on JBRULES-3302:
--------------------------------------------------
Ryan Zhang <rzhang(a)redhat.com> changed the Status of [bug
768952|https://bugzilla.redhat.com/show_bug.cgi?id=768952] from MODIFIED to ON_QA
Unwanted type coersion of String to float values when using
"in" keyword LHS
----------------------------------------------------------------------------
Key: JBRULES-3302
URL: https://issues.jboss.org/browse/JBRULES-3302
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.Final, 5.3.0.Final
Environment: Windows 7, Rational Application Developer 7.5, Eclipse Helios
Service Release 2
Reporter: Troy Parrish
Assignee: Mario Fusco
Fix For: 5.4.0.Beta2
String values get treated as float values even when fact declares the property as a
String when using the "in" keyword to evaluate a String value against a set of
values in the lhs of the rule.
Example:
input into session : "10.5"
will match against all of the following values "10.5", "10.50",
"10.500" etc when in this format:
when
Fact(string in ("11.5", "10.50", "11.500"))
then
This problem behavior occurs in 5.3.0Final, 5.2.0.Final but not in 5.1.0Final, this is
when Expert went from using mvel 2.0.16 to mvel 2.1.0
Further information based on recent findings (12/02/2011)
When inserting a Fact with a Property that is an Object and the LHS references a property
of that object there is the unwanted type coercion even in 5.1.0Final
IE:
Class BigTest has two properties: Test and id. Test is an Object with a single property:
code.
If we reference in the LHS BigTest(test.code in (.....)) we get the unwanted coercion,
but when we reference BigTest(id in (.....)) the coercion does not occur. This is for
5.1.0Final. We find that the coercion takes place for both the syntax of BigTest(id in
(......)) and BigTest(test.code in (.....)) when using 5.2.0Final and up. Example code
below:
CLASSES:
public class BigTest {
private Test test;
private String id;
getters and setters .....
public class Test {
private String code;
getters and setters .....
DRL:
rule "Test.Code One"
when
BigTest($code : test.code in ("1.50", "2.50"))
then
System.out.println("Code compared values: 1.50, 2.50 - actual code value:
" + $code);
end
rule "Test.Code Two"
when
BigTest($code : test.code in ("1.5", "2.5"))
then
System.out.println("Code compared values: 1.5, 2.5 - actual code value:
" + $code);
end
rule "Big Test ID One"
when
BigTest($id : id in ("3.5", "4.5"))
then
System.out.println("ID compared values: 3.5, 4.5 - actual ID value: " +
$id);
end
rule "Big Test ID Two"
when
BigTest($id : id in ( "3.0", "4.0"))
then
System.out.println("ID compared values: 3.0, 4.0 - actual ID value: " +
$id);
end
--
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:46 a.m.
[
https://issues.jboss.org/browse/JBRULES-3302?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration commented on JBRULES-3302:
--------------------------------------------------
Jiri Svitak <jsvitak(a)redhat.com> changed the Status of [bug
768952|https://bugzilla.redhat.com/show_bug.cgi?id=768952] from ON_QA to VERIFIED
Unwanted type coersion of String to float values when using
"in" keyword LHS
----------------------------------------------------------------------------
Key: JBRULES-3302
URL: https://issues.jboss.org/browse/JBRULES-3302
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.Final, 5.3.0.Final
Environment: Windows 7, Rational Application Developer 7.5, Eclipse Helios
Service Release 2
Reporter: Troy Parrish
Assignee: Mario Fusco
Fix For: 5.4.0.Beta2
String values get treated as float values even when fact declares the property as a
String when using the "in" keyword to evaluate a String value against a set of
values in the lhs of the rule.
Example:
input into session : "10.5"
will match against all of the following values "10.5", "10.50",
"10.500" etc when in this format:
when
Fact(string in ("11.5", "10.50", "11.500"))
then
This problem behavior occurs in 5.3.0Final, 5.2.0.Final but not in 5.1.0Final, this is
when Expert went from using mvel 2.0.16 to mvel 2.1.0
Further information based on recent findings (12/02/2011)
When inserting a Fact with a Property that is an Object and the LHS references a property
of that object there is the unwanted type coercion even in 5.1.0Final
IE:
Class BigTest has two properties: Test and id. Test is an Object with a single property:
code.
If we reference in the LHS BigTest(test.code in (.....)) we get the unwanted coercion,
but when we reference BigTest(id in (.....)) the coercion does not occur. This is for
5.1.0Final. We find that the coercion takes place for both the syntax of BigTest(id in
(......)) and BigTest(test.code in (.....)) when using 5.2.0Final and up. Example code
below:
CLASSES:
public class BigTest {
private Test test;
private String id;
getters and setters .....
public class Test {
private String code;
getters and setters .....
DRL:
rule "Test.Code One"
when
BigTest($code : test.code in ("1.50", "2.50"))
then
System.out.println("Code compared values: 1.50, 2.50 - actual code value:
" + $code);
end
rule "Test.Code Two"
when
BigTest($code : test.code in ("1.5", "2.5"))
then
System.out.println("Code compared values: 1.5, 2.5 - actual code value:
" + $code);
end
rule "Big Test ID One"
when
BigTest($id : id in ("3.5", "4.5"))
then
System.out.println("ID compared values: 3.5, 4.5 - actual ID value: " +
$id);
end
rule "Big Test ID Two"
when
BigTest($id : id in ( "3.0", "4.0"))
then
System.out.println("ID compared values: 3.0, 4.0 - actual ID value: " +
$id);
end
--
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:46 a.m.
[
https://issues.jboss.org/browse/JBRULES-3302?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration commented on JBRULES-3302:
--------------------------------------------------
Jiri Svitak <jsvitak(a)redhat.com> made a comment on [bug
768952|https://bugzilla.redhat.com/show_bug.cgi?id=768952]
Verified in BRMS 5.3 ER4.
Unwanted type coersion of String to float values when using
"in" keyword LHS
----------------------------------------------------------------------------
Key: JBRULES-3302
URL: https://issues.jboss.org/browse/JBRULES-3302
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.Final, 5.3.0.Final
Environment: Windows 7, Rational Application Developer 7.5, Eclipse Helios
Service Release 2
Reporter: Troy Parrish
Assignee: Mario Fusco
Fix For: 5.4.0.Beta2
String values get treated as float values even when fact declares the property as a
String when using the "in" keyword to evaluate a String value against a set of
values in the lhs of the rule.
Example:
input into session : "10.5"
will match against all of the following values "10.5", "10.50",
"10.500" etc when in this format:
when
Fact(string in ("11.5", "10.50", "11.500"))
then
This problem behavior occurs in 5.3.0Final, 5.2.0.Final but not in 5.1.0Final, this is
when Expert went from using mvel 2.0.16 to mvel 2.1.0
Further information based on recent findings (12/02/2011)
When inserting a Fact with a Property that is an Object and the LHS references a property
of that object there is the unwanted type coercion even in 5.1.0Final
IE:
Class BigTest has two properties: Test and id. Test is an Object with a single property:
code.
If we reference in the LHS BigTest(test.code in (.....)) we get the unwanted coercion,
but when we reference BigTest(id in (.....)) the coercion does not occur. This is for
5.1.0Final. We find that the coercion takes place for both the syntax of BigTest(id in
(......)) and BigTest(test.code in (.....)) when using 5.2.0Final and up. Example code
below:
CLASSES:
public class BigTest {
private Test test;
private String id;
getters and setters .....
public class Test {
private String code;
getters and setters .....
DRL:
rule "Test.Code One"
when
BigTest($code : test.code in ("1.50", "2.50"))
then
System.out.println("Code compared values: 1.50, 2.50 - actual code value:
" + $code);
end
rule "Test.Code Two"
when
BigTest($code : test.code in ("1.5", "2.5"))
then
System.out.println("Code compared values: 1.5, 2.5 - actual code value:
" + $code);
end
rule "Big Test ID One"
when
BigTest($id : id in ("3.5", "4.5"))
then
System.out.println("ID compared values: 3.5, 4.5 - actual ID value: " +
$id);
end
rule "Big Test ID Two"
when
BigTest($id : id in ( "3.0", "4.0"))
then
System.out.println("ID compared values: 3.0, 4.0 - actual ID value: " +
$id);
end
--
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
10:39 p.m.
[
https://issues.jboss.org/browse/JBRULES-3302?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration commented on JBRULES-3302:
--------------------------------------------------
Anne-Louise Tangring <atangrin(a)redhat.com> made a private comment on [bug
768952|https://bugzilla.redhat.com/show_bug.cgi?id=768952]
Unwanted type coersion of String to float values when using
"in" keyword LHS
----------------------------------------------------------------------------
Key: JBRULES-3302
URL: https://issues.jboss.org/browse/JBRULES-3302
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.Final, 5.3.0.Final
Environment: Windows 7, Rational Application Developer 7.5, Eclipse Helios
Service Release 2
Reporter: Troy Parrish
Assignee: Mario Fusco
Fix For: 5.4.0.Beta2
String values get treated as float values even when fact declares the property as a
String when using the "in" keyword to evaluate a String value against a set of
values in the lhs of the rule.
Example:
input into session : "10.5"
will match against all of the following values "10.5", "10.50",
"10.500" etc when in this format:
when
Fact(string in ("11.5", "10.50", "11.500"))
then
This problem behavior occurs in 5.3.0Final, 5.2.0.Final but not in 5.1.0Final, this is
when Expert went from using mvel 2.0.16 to mvel 2.1.0
Further information based on recent findings (12/02/2011)
When inserting a Fact with a Property that is an Object and the LHS references a property
of that object there is the unwanted type coercion even in 5.1.0Final
IE:
Class BigTest has two properties: Test and id. Test is an Object with a single property:
code.
If we reference in the LHS BigTest(test.code in (.....)) we get the unwanted coercion,
but when we reference BigTest(id in (.....)) the coercion does not occur. This is for
5.1.0Final. We find that the coercion takes place for both the syntax of BigTest(id in
(......)) and BigTest(test.code in (.....)) when using 5.2.0Final and up. Example code
below:
CLASSES:
public class BigTest {
private Test test;
private String id;
getters and setters .....
public class Test {
private String code;
getters and setters .....
DRL:
rule "Test.Code One"
when
BigTest($code : test.code in ("1.50", "2.50"))
then
System.out.println("Code compared values: 1.50, 2.50 - actual code value:
" + $code);
end
rule "Test.Code Two"
when
BigTest($code : test.code in ("1.5", "2.5"))
then
System.out.println("Code compared values: 1.5, 2.5 - actual code value:
" + $code);
end
rule "Big Test ID One"
when
BigTest($id : id in ("3.5", "4.5"))
then
System.out.println("ID compared values: 3.5, 4.5 - actual ID value: " +
$id);
end
rule "Big Test ID Two"
when
BigTest($id : id in ( "3.0", "4.0"))
then
System.out.println("ID compared values: 3.0, 4.0 - actual ID value: " +
$id);
end
--
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
10:10 p.m.
[
https://issues.jboss.org/browse/JBRULES-3302?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration commented on JBRULES-3302:
--------------------------------------------------
Anne-Louise Tangring <atangrin(a)redhat.com> made a private comment on [bug
768952|https://bugzilla.redhat.com/show_bug.cgi?id=768952]
Unwanted type coersion of String to float values when using
"in" keyword LHS
----------------------------------------------------------------------------
Key: JBRULES-3302
URL: https://issues.jboss.org/browse/JBRULES-3302
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.Final, 5.3.0.Final
Environment: Windows 7, Rational Application Developer 7.5, Eclipse Helios
Service Release 2
Reporter: Troy Parrish
Assignee: Mario Fusco
Fix For: 5.4.0.Beta2
String values get treated as float values even when fact declares the property as a
String when using the "in" keyword to evaluate a String value against a set of
values in the lhs of the rule.
Example:
input into session : "10.5"
will match against all of the following values "10.5", "10.50",
"10.500" etc when in this format:
when
Fact(string in ("11.5", "10.50", "11.500"))
then
This problem behavior occurs in 5.3.0Final, 5.2.0.Final but not in 5.1.0Final, this is
when Expert went from using mvel 2.0.16 to mvel 2.1.0
Further information based on recent findings (12/02/2011)
When inserting a Fact with a Property that is an Object and the LHS references a property
of that object there is the unwanted type coercion even in 5.1.0Final
IE:
Class BigTest has two properties: Test and id. Test is an Object with a single property:
code.
If we reference in the LHS BigTest(test.code in (.....)) we get the unwanted coercion,
but when we reference BigTest(id in (.....)) the coercion does not occur. This is for
5.1.0Final. We find that the coercion takes place for both the syntax of BigTest(id in
(......)) and BigTest(test.code in (.....)) when using 5.2.0Final and up. Example code
below:
CLASSES:
public class BigTest {
private Test test;
private String id;
getters and setters .....
public class Test {
private String code;
getters and setters .....
DRL:
rule "Test.Code One"
when
BigTest($code : test.code in ("1.50", "2.50"))
then
System.out.println("Code compared values: 1.50, 2.50 - actual code value:
" + $code);
end
rule "Test.Code Two"
when
BigTest($code : test.code in ("1.5", "2.5"))
then
System.out.println("Code compared values: 1.5, 2.5 - actual code value:
" + $code);
end
rule "Big Test ID One"
when
BigTest($id : id in ("3.5", "4.5"))
then
System.out.println("ID compared values: 3.5, 4.5 - actual ID value: " +
$id);
end
rule "Big Test ID Two"
when
BigTest($id : id in ( "3.0", "4.0"))
then
System.out.println("ID compared values: 3.0, 4.0 - actual ID value: " +
$id);
end
--
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
5:34 a.m.
[
https://issues.jboss.org/browse/JBRULES-3302?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration commented on JBRULES-3302:
--------------------------------------------------
lcarlon <lcarlon(a)redhat.com> made a comment on [bug
768952|https://bugzilla.redhat.com/show_bug.cgi?id=768952]
Technical note added. If any revisions are required, please edit the "Technical
Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services
team.
New Contents:
When the 'in' keyword is used to evaluate a String value against a set of values
in the LHS of the rule, the String is treated as a float value. This was caused by a wrong
type coercion in MVEL. The issue has been resolved and String values are now treated as
Strings when used with the 'in' keyword.
Unwanted type coersion of String to float values when using
"in" keyword LHS
----------------------------------------------------------------------------
Key: JBRULES-3302
URL: https://issues.jboss.org/browse/JBRULES-3302
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.Final, 5.3.0.Final
Environment: Windows 7, Rational Application Developer 7.5, Eclipse Helios
Service Release 2
Reporter: Troy Parrish
Assignee: Mario Fusco
Fix For: 5.4.0.Beta2
String values get treated as float values even when fact declares the property as a
String when using the "in" keyword to evaluate a String value against a set of
values in the lhs of the rule.
Example:
input into session : "10.5"
will match against all of the following values "10.5", "10.50",
"10.500" etc when in this format:
when
Fact(string in ("11.5", "10.50", "11.500"))
then
This problem behavior occurs in 5.3.0Final, 5.2.0.Final but not in 5.1.0Final, this is
when Expert went from using mvel 2.0.16 to mvel 2.1.0
Further information based on recent findings (12/02/2011)
When inserting a Fact with a Property that is an Object and the LHS references a property
of that object there is the unwanted type coercion even in 5.1.0Final
IE:
Class BigTest has two properties: Test and id. Test is an Object with a single property:
code.
If we reference in the LHS BigTest(test.code in (.....)) we get the unwanted coercion,
but when we reference BigTest(id in (.....)) the coercion does not occur. This is for
5.1.0Final. We find that the coercion takes place for both the syntax of BigTest(id in
(......)) and BigTest(test.code in (.....)) when using 5.2.0Final and up. Example code
below:
CLASSES:
public class BigTest {
private Test test;
private String id;
getters and setters .....
public class Test {
private String code;
getters and setters .....
DRL:
rule "Test.Code One"
when
BigTest($code : test.code in ("1.50", "2.50"))
then
System.out.println("Code compared values: 1.50, 2.50 - actual code value:
" + $code);
end
rule "Test.Code Two"
when
BigTest($code : test.code in ("1.5", "2.5"))
then
System.out.println("Code compared values: 1.5, 2.5 - actual code value:
" + $code);
end
rule "Big Test ID One"
when
BigTest($id : id in ("3.5", "4.5"))
then
System.out.println("ID compared values: 3.5, 4.5 - actual ID value: " +
$id);
end
rule "Big Test ID Two"
when
BigTest($id : id in ( "3.0", "4.0"))
then
System.out.println("ID compared values: 3.0, 4.0 - actual ID value: " +
$id);
end
--
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
4355
days inactive
4539
days old
19 comments
6 participants
participants (6)
-
Alessandro Lazarotti (Assigned) (JIRA) -
Alessandro Lazarotti (JIRA)
-
Mario Fusco (JIRA)
-
RH Bugzilla Integration (JIRA)
-
Troy Parrish (Created) (JIRA)
-
Troy Parrish (Updated) (JIRA)