Condition sharing is maybe one, the other being that there is possibly a
little more work being done. But its probably marginal in Drools 2. If it
makes you rules much neater, its probably fine to use it unless you are
noticing a specific performance problem.
On 2/28/06, Peter Van Weert <[EMAIL PROTECTED]> wrote:
>
> Just out of curiosity: why is it a bad idea to use || in conditions?
>
> Paul Smith wrote:
>
> I've used it in a few conditions along with &&.Given these comments
> though I'll rework them into separate conditions.
>
> On 2/27/06, Mark Proctor <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> wrote:
>
> Anagha,
>
> Its not a good idea to use || in conditions - instead write out two
> rules for the different outcomes. However I thought that || had been
> made allowed in conditions, for those that insist on using it - has
> anyone else been able to use || in conditions? If || has not been yet
> made available i'm afraid you will have to wait till 3.0.
>
> Mark
> Anagha wrote:
>
> Hi All,
> I'm using drools-2.1 with java semantics.
> I want to combine multiple condtions in a single condition with OR.
> i.e. if * (hello.equals("Hi") || hello.equals("Hey")
> But it seems "java.xsd" does not allow such type of constructs in the
> "condition".
> Any ideas?
>
> Any help is welcome.
>
> --
> Thanks & Regards,
> Anagha
>
>
>
>
