I'm not sure this will help you out, but in what comes to the system i'm currently developing (using drools expert), i've got this method "runRuleEngine" that collects facts and fire rules on them and i am able to catch any sort of error within the drools execution by surrounding that with try {} catch (Exception e) {}.

The important part is that it took me a while to figure that out cuz eclipse didn't force me handle that, as if the called method didn't have "throws" (it usually shows a compilation error otherwise, right?).

On Wed, Mar 31, 2010 at 9:44 PM, nanic23 <nanic23@hotmail.com> wrote:

I have a ruleflow that handles exceptions when they are raised by a "Fault"
node but I am not being able to accomplish the same if an exception is
thrown by a workItem or an action node instead.

I have a workItem node with a work item handler that throws a
RuntimeException. My exception handler in the composite node is not catching
this exception.

So, question
1) how can I handle runtime exceptions thrown by my workItemHandlers?
2) how can I get a hold of the exception to log the stack trace?

Any ideas or tips are very appreciated.

Nick.
--
View this message in context: http://n3.nabble.com/How-to-do-Exception-Handling-tp689387p689387.html
Sent from the Drools - User mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users

--
"To understand what is recursion you must first understand recursion"