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 127434 - Breakpoint isn't displayed in design view when set on elements not shown on the diagram
Summary: Breakpoint isn't displayed in design view when set on elements not shown on t...
Status: NEW
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Debugger (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: issues@soa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-15 00:45 UTC by Ivan Sidorkin
Modified: 2009-03-06 13:56 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan Sidorkin 2008-02-15 00:45:54 UTC 
Product Version: NetBeans IDE Dev (Build 200802140010)
Java: 1.6.0_04; Java HotSpot(TM) Client VM 10.0-b19
System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb)

- create SynchronousSample
- open SynchronousSample.bpel in source view
- put cursor to copy tag 
- press Ctrl-F8
- breakpoint added
- switch to Design view

you can't see breakpoint
Comment 1 Sergey Lunegov 2008-02-15 06:50:28 UTC 
changed target milestone
Comment 2 Kirill Sorokin 2008-02-20 22:31:43 UTC 
The only case when a breakpoint is not shown in Design view is when it is set on an element, which, in turn, is not
shown on the diagram either. So far these are only <copy> and <condition> sub-activities. The same behavior (not being
shown on the diagram) can be observed when stepping through the activities while debugging.

At the same time, the user can easily see what's happening if he takes a look at the navigator, or sources view. Thus
lowering to P4 and marking as to be fixed in the future, when these elements become available on the diagram.

Note also, that the user cannot set breakpoints on these element from the diagram directly. This lowers the probability
of this issue being exposed to the user even more.