[
http://jira.jboss.com/jira/browse/JBRULES-1289?page=comments#action_12410436 ]
Michael Neale commented on JBRULES-1289:
----------------------------------------
Most likely a case of capturing an error at the right spot, failing that, then catching an
exception, and if it is more to do with syntax - just have a more polite message rather
then a stack trace. Even if we cant narrow it down to a line, we can at least say there
was an error, the stack trace does not help here at all.
BRMS gives unusable error messages when validating DSL based rules
------------------------------------------------------------------
Key: JBRULES-1289
URL:
http://jira.jboss.com/jira/browse/JBRULES-1289
Project: JBoss Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-brms
Affects Versions: 4.0.2
Reporter: Phil Verghese
Assigned To: Michael Neale
The error messages that are shown when you click "Validate" when editing a
business rule that uses a DSL in the BRMS are not user-friendly at all. If I make a small
typo and misspell the name of an attribute (a very likely thing for a BRMS user to do),
and click the Validate button, the error I get back is a big stack trace starting with
"java.lang.RuntimeException: SNO: Conversion failed at
org.codehaus.janino.UnitCompiler.numericPromotion(UnitCompiler.java) at ..." Nowhere
in that stack trace is anything that gives a hint that
the error is just a typo of an attribute name.
Contrast this with the rather helpful error message I get if I make the same typo when
editing a DRL rule: "Unable to create Field Extractor for
'overtimHours'". (The error is that I misspelled overtimeHours).
The BRMS needs to give the same type of helpful error message on validation errors when
editing a DSL rule.
--
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