[jboss-jira] [JBoss JIRA] (JBRULES-3676) drl cann't debuging in Eclipse IDE

[Mattias Nilsson Grip (JIRA)]

    [ https://issues.jboss.org/browse/JBRULES-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733701#comment-12733701 ] 

Mattias Nilsson Grip commented on JBRULES-3676:
-----------------------------------------------

I have analyzed this and found that it is possible to debug rules in MVEL dialect but not Java dialect. The problem seems to have been introduced by the fix for JBRULES-3267. To fix a problem that can happen when multiple threads simultaneously update the same knowledge base, that bug fix added a random UUID string to the name of generated Java class for rule consequences.

The problem is that the randomness of the class names for Java rules makes it impossible for the Eclipse debugger to know what Java class to map the DRL breakpoint to.

I have made pull requests that provides a suggested fix for the problem. I added a system property that can be used to turn on/off the UUID part of the class names. It is on by default but off when debugging in Eclipse as a "Drools Application":

https://github.com/droolsjbpm/drools/pull/165
https://github.com/droolsjbpm/droolsjbpm-tools/pull/13
                
> drl cann't debuging in Eclipse IDE
> ----------------------------------
>
>                 Key: JBRULES-3676
>                 URL: https://issues.jboss.org/browse/JBRULES-3676
>             Project: Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-core  (expert)
>    Affects Versions: 5.5.0.CR1
>         Environment: Eclipse 4.2，JDK1.7，Drools5.5CR1
>            Reporter: hongkun an
>            Assignee: Mark Proctor
>
> i follow url content
> http://docs.jboss.org/drools/release/5.2.0.Final/drools-expert-docs/html/ch08.html
> I want debug drl example（HelloWord）in eclipse ide，but，only debug java file，cann't debug drl，why？

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira