yes Exceptions should not be thrown as part of normal processing as they can seriously effect perforamnce, but if it is unavoidable, use a function or wrap some objects to catch them.
On 4/11/06, Mark Proctor <[EMAIL PROTECTED]> wrote: > > Not at the moment, as we consider the working memory to have an invalid > state at this point. I'm not sure adding this is a good idea. Exceptions > are not generally considered recoverably. What you can do is have the > eval call a function, which wraps and swalls the thrown exception. > > Mark > Juergen wrote: > > Is it possible to tell drools not to forward an exception thrown > > during LHS evaluation, but to consider it as LHS not fulfilled? > > probably as additional rule attribute? > > > > e.g. > > rule "a" > > failureException NullPointerException, SomeException > > when > > a : A() > > B(b == > > (aBind.getSomeAttrib().getSomeAttribThatsNull().getAttrib()) > > eval ( someExpressionsThatThrowsSomeException() ) > > then > > ... > > end > > > > > > > >
