Thanks,
Yes I tried & it's working fine on our server running Drool. 5.1.
--
View this message in context:
http://drools.46999.n3.nabble.com/Getting-java-lang-ClassCastException-using-Drools-5-3-tp3785966p3791434.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
_
On 29 February 2012 15:21, kashif10 wrote:
>
> One more question, is it work with Drool 5.1 too?
>
Inline eval() works with 5.1 and later.
> I already went through Drool Documents found on the official site, but is
> there any resource to learn more about the syntax?
>
>
You can learn a lot f
Thanks a lot Laune, for the suggestion,
I was adding eval condition using "and", as I thought that I can't add eval
condition using $Dx1 inside the $DX1 matching assignment. but your
suggestion working fine, by putting eval inside the $Dx1 assignment
matching.
As far as generalize Facts bean is
This is a bug in the DRL parser/builder. Even when you (as you should)
omit the parentheses around the patterns "Medication" and "Procedure"
(see below) you get the same exception:
( $Dx1 : Medication( name == "Oflo" )
and
eval($x.check($Dx1) )
)
or
( $Dx2 : Procedure( name == "Pr
HI.
I am getting following exception.
Exception in thread "main" org.drools.RuntimeDroolsException:
d1.rule.Rule_8f09c0aa35010080cb1e0dd40f6fEval4Invoker@f6f66af4 :*
java.lang.ClassCastException: d1.rule.facts.Medication cannot be cast to
d1.rule.facts.Procedure*
at org.drools.rule.Eva
