Bug 724232 (BRMS-176) - MVEL debug not working anymore
Summary: MVEL debug not working anymore
Keywords:
Status: CLOSED NEXTRELEASE
Alias: BRMS-176
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: unspecified
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: 5.0.1
Assignee: Kris Verlaenen
QA Contact:
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-07 15:08 UTC by nwallace
Modified: 2009-10-05 08:30 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-01 12:27:01 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-176 0 None None None Never

Description nwallace 2009-07-07 15:08:27 UTC
Date of First Response: 2009-09-10 01:26:40
securitylevel_name: Public

When debugging rules using the MVEL dialect, Eclipse cannot find the right MVEL source and line number to show when encountering a breakpoint in MVEL code.

Comment 1 nwallace 2009-07-07 15:09:47 UTC
Link: Added: This issue is related to JBRULES-2071


Comment 2 nwallace 2009-09-01 12:27:01 UTC
Fix in place.

Comment 3 David Le Sage 2009-09-10 05:26:40 UTC
For documenting this in the Release Notes, can you please confirm the following and fill in the missing information. Dot point explanations are fine:

The CAUSE (what was actually broken)
 *  changes to the MVELFrame class (which was an external MVEL dependency) caused a problem

CONSEQUENCES of the bug (how it impacts users.)
 * the way in which the IDE retrieved the source file number and line number at breakpoints no longer worked.

The FIX (what was changed to eliminate this bug) and 
 *

RESULTS of the fix (what now happens for users.)
 * 

Comment 4 David Le Sage 2009-09-23 05:39:32 UTC
We are still awaiting the outstanding information for the Release Notes on this one.  Please provide it as soon as possible. Thanks.

Comment 5 Kris Verlaenen 2009-09-23 13:04:49 UTC
The CAUSE (what was actually broken)
 * changes to the MVELFrame class (which was an external MVEL dependency) caused a problem during MVEL debug

CONSEQUENCES of the bug (how it impacts users.)
 * the way in which the IDE retrieved the source file number and line number at breakpoints no longer worked.

The FIX (what was changed to eliminate this bug) and
 * code changed to take MVEL changes into account

RESULTS of the fix (what now happens for users.)
 * MVEL debugging working again


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