Joshua,
The limitation is on binding variables on different fact types on
different logical branches and using them in the consequence. If you don't
use the bindings in the consequence, you are fine.
This is a temporary limitation.
[]s
Edson
2008/3/7, Joshua Undesser <[EMAIL PROT
Thank you Mark for the quick reply. I am curious if this is only temporary
or if this is the protocol that Drools is going to use for "or" statements?
The reason I ask is that i come from a jess/clips background, where "or" can
be used across multiple classes as shown in my example and it is v
Mark Proctor wrote:
The 'or' must be used for classes of the same type.
Also there was some 'or' issues fixed for 4.0.5. You can test this from
the 4.0.x branch, let us know if it fixes all your problems.
http://anonsvn.labs.jboss.com/labs/jbossrules/branches/4.0.x/
Mark
Joshua Undesser wrote
The 'or' must be used for classes of the same type.
Mark
Joshua Undesser wrote:
I am curious if anyone else has run into this problem.It seems like there
is something wrong in the Drools LogicMy issue can be very easily be
recreated in about 5 minutes
>From eclipse I set up a new dr
I am curious if anyone else has run into this problem.It seems like there
is something wrong in the Drools LogicMy issue can be very easily be
recreated in about 5 minutes
>From eclipse I set up a new drools project.Where DroolTest.java is
defined I create 4 new classes, ClassA,
