I have found that any serious Drools application should write and deploy a
consequence exception handler of its own. Perhaps you look at my modest
effort<http://members.inode.at/w.laun/drools/CustomConsequenceExceptionHandlingHowTo.html>-
I think it is still compatible. Any feedback welcome ;-)
-W
On 4 October 2011 04:46, lhorton <LHorton(a)abclegal.com> wrote:
This is very good info. I have found those Drools
ConsequenceExceptions a
real PITA to troubleshoot. I wonder if the exception could be enhanced to
show this info so users don't have to debug it? I mean, to have the
exception message show the true culprit rule name, or something useful like
that?
--
View this message in context:
http://drools.46999.n3.nabble.com/5-3-0-CR1-has-broken-existing-rules-flo...
Sent from the Drools: User forum mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users