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 122740

Summary: Provide a capability for a debugger engine to define its own set of views
Product: debugger Reporter: Kirill Sorokin <ksorokin>
Component: CodeAssignee: Martin Entlicher <mentlicher>
Status: CLOSED DUPLICATE    
Severity: blocker CC: ivan, ivansidorkin
Priority: P2    
Version: 6.x   
Hardware: All   
OS: All   
Issue Type: ENHANCEMENT Exception Reporter:
Bug Depends on:    
Bug Blocks: 126927    

Description Kirill Sorokin 2007-11-26 06:57:42 UTC
Currently if one requires a special view in the debugger group, he needs to add it to the standard 'debugger' view
group, which would result in this view being shown whenever ANY debug session starts, whether or not the current engine
needs this view.

It would be very nice if one could define the debugger view group on a per-engine basis. This way we wouldn't have to
show the nonsensical (in that context) Call Stack view when debugging BPEL and vice-versa, the BPEL Process Execution
view would be hidden when debugging java.
Comment 1 Martin Entlicher 2008-04-24 15:19:59 UTC
Currently the opened/closed state of debugger views is hard-coded in debuggercore module. All windows with opened state
that belongs to debugger group are opened.

DebuggerManagerListener can check some property on the current DebuggerEngine and open/close the windows accordingly...
Comment 2 Martin Entlicher 2008-05-13 21:32:32 UTC

*** This issue has been marked as a duplicate of 81926 ***
Comment 3 Quality Engineering 2010-04-29 09:37:22 UTC
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.