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 126927 - BPEL debugger view opened for plain java project
Summary: BPEL debugger view opened for plain java project
Status: VERIFIED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Debugger (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Kirill Sorokin
URL:
Keywords:
: 130982 139369 139761 (view as bug list)
Depends on: 81926 122740
Blocks:
  Show dependency tree
 
Reported: 2008-02-07 16:23 UTC by Jiri Skrivanek
Modified: 2008-08-06 14:46 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Skrivanek 2008-02-07 16:23:03 UTC
BPEL Partner Links, BPEL Process Execution and BPEL Process Instances views are opened when you start debugger for a
plain java project. To reproduce:

- create a java project
- add some code to Main.java and toggle breakpoint
- start debugger and above mentioned BPEL views are opened.

Product Version: NetBeans IDE Dev (Build 20080207133332)
Java: 1.6.0_04; Java HotSpot(TM) Client VM 10.0-b19
System: Windows XP version 5.1 running on x86; Cp1250; cs_CZ (nb)
Comment 1 Kirill Sorokin 2008-02-07 16:45:21 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.
Comment 2 Kirill Sorokin 2008-03-25 09:26:24 UTC
*** Issue 130982 has been marked as a duplicate of this issue. ***
Comment 3 Marian Mirilovic 2008-03-25 09:42:11 UTC
This is really annoying - what about defining your own group of debugger windows ?
Comment 4 Kirill Sorokin 2008-03-25 10:20:00 UTC
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. :)
Comment 5 Sergey Lunegov 2008-03-28 09:35:56 UTC
Waived.
Comment 6 Martin Entlicher 2008-06-06 19:03:05 UTC
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
Comment 7 Kirill Sorokin 2008-07-09 11:31:23 UTC
*** Issue 139369 has been marked as a duplicate of this issue. ***
Comment 8 Kirill Sorokin 2008-07-11 22:52:14 UTC
*** Issue 139761 has been marked as a duplicate of this issue. ***
Comment 9 Joelle Lam 2008-07-11 23:18:27 UTC
Is this schedule for M2? or just 6.5?
Comment 10 Kirill Sorokin 2008-07-11 23:42:41 UTC
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.
Comment 11 Kirill Sorokin 2008-08-04 10:24:04 UTC
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.
Comment 12 Jiri Skrivanek 2008-08-06 14:46:00 UTC
Verified.