Interesting bug.. could also be a problem of windows + galileo?
On Mon, Aug 10, 2009 at 5:10 PM, Marc Dzaebel wrote:
>
>
> Mauricio Salatino wrote:
> >
> > It's weird that it doesn't work if you don't put that.. that must be the
> > default value..
> I isolated the problem to reseting the node t
Mauricio Salatino wrote:
>
> It's weird that it doesn't work if you don't put that.. that must be the
> default value..
I isolated the problem to reseting the node type from OR to AND which
doesn't clean the constraint information correctly. The workaround is to
simply reinsert the node + const
It's weird that it doesn't work if you don't put that.. that must be the
default value..
2009/8/10 Marc Dzaebel
> The process works, if I insert *toType="DROOLS_DEFAULT"* into the *
> constraint* nodes.
> --
> View this message in context: Re: Drools 5 RuleFlow error
The process works, if I insert toType="DROOLS_DEFAULT" into the constraint
nodes.
--
View this message in context:
http://www.nabble.com/Drools-5-RuleFlow-error-in-constraints-of-simplest-split-node-tp24901923p24904785.html
Sent from the drools - user mailing list archive at Nabble.com.
Mauricio Salatino wrote:
>
> Yes.. that's because you are using an OR split.. it can not support both
> constraints to be true. In other words if you use a type="3" split you
> don't
> need to put that constraints because just one will be triggered.
> If you want an XOR or an AND split change th
Yes.. that's because you are using an OR split.. it can not support both
constraints to be true. In other words if you use a type="3" split you don't
need to put that constraints because just one will be triggered.
If you want an XOR or an AND split change the type of the split node. (
type="3")
