Bug 1253575 - Drools nested date comparison expressions with OR condition
Summary: Drools nested date comparison expressions with OR condition
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: BRE
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ER3
: 6.2.0
Assignee: Mario Fusco
QA Contact: Marek Winkler
URL:
Whiteboard:
Depends On:
Blocks: 1253576
TreeView+ depends on / blocked
 
Reported: 2015-08-14 06:59 UTC by Hisao Furuichi
Modified: 2020-03-27 20:12 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1253576 (view as bug list)
Environment:
Last Closed: 2020-03-27 20:12:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Hisao Furuichi 2015-08-14 06:59:03 UTC
Description of problem:

Following RHS which uses Date object comparison works fine:

DateContainer( date >= "15-Oct-2013" || date <= "01-Oct-2013" )

If there are multiple conditions connecting with "||" or "&&" as follows, syntax error occurs:

DateContainer ( (date >= "19-Dec-2015" && date <= "03-Jan-2016" ) || (date >= "17-Dec-2016" && date <= "02-Jan-2017" ))	

Exception is

===
Unable to Analyse Expression date >= "19-Dec-2015" && date <= "03-Jan-2016" || date >= "17-Dec-2016" && date <= "02-Jan-2017":
[Error: Comparison operation requires compatible types. Found class java.util.Date and class java.lang.String]
[Near : {... "03-Jan-2016" || date >= "17-Dec-2016" && date <= "02-Jan-2017" ....}]
                                                               ^
[Line: 25, Column: 2]
===

Additional info:
BZ-1072217 covers non-nested comparison like this:

DateContainer( date >= "15-Oct-2013" || date <= "01-Oct-2013" )

Comment 1 Hisao Furuichi 2015-08-14 07:00:02 UTC
I tested with BRMS 6.1.2, and the issue still occurs.

Comment 2 Mario Fusco 2015-08-18 09:37:35 UTC
Fixed by https://github.com/droolsjbpm/drools/commit/dc81e1f1c

Comment 3 Marek Winkler 2015-10-08 15:01:04 UTC
Verified in BRMS 6.2.0 ER3.


Note You need to log in before you can comment on or make changes to this bug.