This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 78137 - BPEL Debugger should somehow indicate breakpoints that are not applicable
Summary: BPEL Debugger should somehow indicate breakpoints that are not applicable
Status: CLOSED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Debugger (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: Alexander Zgursky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-16 15:21 UTC by bugbridge
Modified: 2006-08-31 02:02 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bugbridge 2006-06-16 15:21:38 UTC
Description:
There are lots of situation when a breakpoint set by user will be ignored by
debugger.
These are various situations when breakpoint is not set inside an activity: at
<variables> tag, at <catch> or <catchAll> tag, etc...

There should be a way to tell user that debugger misses these breakpoints
because they are set at wrong positions. Possible options can be writing message
to output or changing annotation color.
Comment 1 Alexander Zgursky 2006-08-03 13:08:11 UTC
Fixed. It's now impossible to put a breakpoint at invalid position and if bpel
file becomes invalid or the element for the breakpoint gets removed the
breakpoint annotations are removed and breakpoint is shown as "(invalid)" in the
Breakpoints View. When bpel file becomes valid again breakponts annotations are
recovered and the Breakpoints View is updated.
Comment 2 lchang 2006-08-04 19:44:54 UTC
When you click to add a breakpoint on somehwere invalid, it won't add the 
breakpoint.