Bug 1253576 - Drools nested date comparison expressions with OR condition
Summary: Drools nested date comparison expressions with OR condition
Keywords:
Status: NEW
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRE (Expert, Fusion)
Version: BRMS 5.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On: 1253575
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-14 07:02 UTC by Hisao Furuichi
Modified: 2024-01-01 01:36 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1253575
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Hisao Furuichi 2015-08-14 07:02:03 UTC
+++ This bug was initially created as a clone of Bug #1253575 +++

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" )

--- Additional comment from Hisao Furuichi on 2015-08-14 03:00:02 EDT ---

I tested with BRMS 6.1.2, and the issue still occurs.

Comment 1 Hisao Furuichi 2015-08-14 07:02:50 UTC
The issue still occurs with BRMS 5.3.1 with rollup patch #5


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