[jboss-jira] [JBoss JIRA] Commented: (JBRULES-118) Map generated .java compilation errors to drl

Mark Proctor (JIRA) jira-events at jboss.com
Sat Sep 2 17:03:43 EDT 2006


    [ http://jira.jboss.com/jira/browse/JBRULES-118?page=comments#action_12342695 ] 
            
Mark Proctor commented on JBRULES-118:
--------------------------------------

yup, but you just fixed that :)
Yes its not a nice solution, as runtime errors will still report the wrong line numbers - unless we "clone" errors replacing with correct filename and line numbers - but this can just get messy with stack traces etc. 
You are right that the whole solution is not that nice, but I can't think of any nicer way with execution of compiled code.

> Map generated .java  compilation errors to  drl
> -----------------------------------------------
>
>                 Key: JBRULES-118
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-118
>             Project: JBoss Rules
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>            Reporter: Mark Proctor
>         Assigned To: Bob McWhirter
>             Fix For: 3.1-m3
>
>
> We know the method name for each descr. If we move the params all onto  a  single line we can use indexof to fine the start of each descr' compiled  code. We can then use that  to find the offiset and map the error  to the descr.
> This is complex as the error handling needs to be reworked. CompilationProblem objects should NOT be stuffed inside rule errors, but be seperate rule errors (hence can have multiple line errors).

-- 
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

        



More information about the jboss-jira mailing list