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.
Summary: | BPEL debugger view opened for plain java project | ||
---|---|---|---|
Product: | soa | Reporter: | Jiri Skrivanek <jskrivanek> |
Component: | BPEL Debugger | Assignee: | Kirill Sorokin <ksorokin> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | CC: | mmirilovic |
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | 81926, 122740 | ||
Bug Blocks: |
Description
Jiri Skrivanek
2008-02-07 16:23:03 UTC
Currently there is no way for us to define a separate set of top components that will be shown for BPEL debugging session and NOT shown for others. :( So we decided that it's better to show everything, instead being forced to hide views that are crucial for BPEL. See the dependent issue. *** Issue 130982 has been marked as a duplicate of this issue. *** This is really annoying - what about defining your own group of debugger windows ? We reuse some of the standard debugger views (Local Variables, Breakpoints, Threads, Watches, etc..). I tried to define a group which consisted of both BPEL-specific and common views, but without much success. Thus I asked for debuggercore's help, hence the dependent issue. They did promise to look @ it. :) Waived. After issue #81926 is fixed, you can return the desired set of components to open in BpelDebuggerEngineProvider.getServices(), via BeanContextChildComponentProxy. And then please remove BPELPLinksView, ProcessView and ProcessExecutionView from "debugger" group in bpel.debugger.ui/build/classes/org/netbeans/modules/bpel/debugger/ui/resources/layer.xml *** Issue 139369 has been marked as a duplicate of this issue. *** *** Issue 139761 has been marked as a duplicate of this issue. *** Is this schedule for M2? or just 6.5? Since the SOA stuff is slightly bound with the necessity to sync with other projects (namely Java CAPS), we're slightly off-track with NetBeans milestones. When is NB 6.5 M2 expected to appear? The current plan is to fix the issue by end of Aug. Fixed. Changesets for {main}: http://hg.netbeans.org/main/rev/a0f30605bc49 http://hg.netbeans.org/main/rev/176136cf3be6 The fix is not applicable for {soa-dev}, so it was not ported there. Verified. |