Bug 1130277 - Add Free Form Java in the Guided Rule Editor needs better error reporting
Summary: Add Free Form Java in the Guided Rule Editor needs better error reporting
Status: NEW
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.2
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: manstis
QA Contact: Jiri Locker
Depends On:
TreeView+ depends on / blocked
Reported: 2014-08-14 19:00 UTC by Jim Tyrrell
Modified: 2016-01-08 22:15 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed:
Type: Enhancement

Attachments (Terms of Use)

Description Jim Tyrrell 2014-08-14 19:00:21 UTC
Description of problem:
When inputting java code, javac like error messages should be pushed to the problems window.  The current messages are very cryptic and not easily figured out.

Version-Release number of selected component (if applicable):

How reproducible:
Any typo or syntax error results in hard to decipher error messages

Steps to Reproduce:
1.System.er.println("Error message");
2. System.err.println(“Fired the first Guided Rule”);
If fancy quotes are cut and pasted from a lab writeup it also won't compile, I am not sure if they copied into here, but pretty sure they were submitted correctly.

Actual results:

Expected results:
Good error messages from javac would be expected.
In the first case, it isn't too bad with the message, "Rule Compilation error er cannot be resolved or is not a field" but it notes file FirstGuidedRule.rdrl.  Which seems odd.

It also references line 5, but in the source code view it is line 10.

In the second example the message is, "[ERR 101] Line 10:21 no viable alternative at input ''" which isn't too bad.  So the line number is right in that output, and the line specific output.  But I have no way to know the column number in the source viewer, could we click in the source and see a 10:20 output that shows line and column info.  It might also be nice to see the line that is in error in the problem tab, instead of a message and the output of the parsed error.

Additional info:

Note You need to log in before you can comment on or make changes to this bug.