This may sound a bit rude, but... why would you want to do such a thing?
If there is a constraint on the message, then why not put that constraint in
the message structure?
Btw, I think it would work by using eval($date < "...") but see no use for
it either.
Joe Zendle wrote
>
> did you try:
>
> *$msg : Message($date : date)
> Order ( $date > "Mar-01-2012" )*
>
>
>
> 2012/3/29 Zeke <xanadu860122@>
>
>> Hi, guys:
>> I meet a strange issue and need your help again... I am using Drools
>> 4.0.7.
>> When my rule condition is as *Message( date > "Mar-01-2012" )*,
>> everything is OK. But if I change it to be as below:
>> *$msg : Message()
>> Order ( $msg.date > "Mar-01-2012" )*
>> I will meet "java.lang.String cannot be cast to java.util.Date"
>> ClassCastException. "Order" is another fact. I attach the exception call
>> stack. Please check it. It looks like a bug to me. Do we fix it in later
>> release? If so, can you tell me which release contains the fix? Thanks!
>>
>> _______________________________________________
>> rules-users mailing list
>> rules-users@.jboss
>> https://lists.jboss.org/mailman/listinfo/rules-users
>>
>>
>
> _______________________________________________
> rules-users mailing list
> rules-users@.jboss
> https://lists.jboss.org/mailman/listinfo/rules-users
>
--
View this message in context: http://drools.46999.n3.nabble.com/rules-users-ClassCastException-when-comparing-date-type-with-literal-tp3867229p3867832.html
Sent from the Drools: User forum mailing list archive at Nabble.com.