[
http://jira.jboss.com/jira/browse/JBRULES-1477?page=all ]
Mark Proctor closed JBRULES-1477.
---------------------------------
Fix Version/s: 4.0.5
5.0.0-M1
Resolution: Done
I've removed the stack trace printout from DefaultConsequenceExceptionHandler.
User exception thrown from inside a rule always causes a stackTrace
to console
------------------------------------------------------------------------------
Key: JBRULES-1477
URL:
http://jira.jboss.com/jira/browse/JBRULES-1477
Project: JBoss Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0.4
Environment: WindowsXP; Drools 4-0-4; Example run from inside Eclipse 3-3-1-1.
Reporter: Dominic Staples
Assigned To: Mark Proctor
Priority: Optional
Fix For: 4.0.5, 5.0.0-M1
Attachments: DroolsStackTraceDemo.zip
I asked for (and immediately received - Thanks!) some assistance via the Drools IRC
webclient regarding throwing exceptions inside rules.
I now know that this is probably a bad thing in most cases, however one of my queries at
the time was how to stop the stacktrace being sent to the console even though the
exception was successfuly caught at the .fireAllRules() invocation.
It was suggested that this was a bug, and could I submit a JIRA - here it is.
Attached is a very basic re-create of the situation. I'm running Drools 4.0.4.
As I've managed to convince my team mates that throwing exceptions from inside rules
is a bad thing, I won't be waiting for a fix :-)
Thanks for a great product,
Dom Staples.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira