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 81141 - Attaching debugger has usability problems
Summary: Attaching debugger has usability problems
Status: CLOSED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Debugger (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Vladimir Yaroslavskiy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-26 10:31 UTC by Mikhail Kondratyev
Modified: 2006-08-04 02:50 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 Mikhail Kondratyev 2006-07-26 10:31:08 UTC
When attaching debuger user has to do several tricky and non-obvious steps, for
example
 - find the com.sun.bpelse-1.0-2 node (the name has no indication that it is
related to debugger)
 - change the DebugEnabled property of the node (although the property name is
OK, how a user may know where to search for this property?)

And only then user will be able to attach the debugger in standard NB way (again
user has to know that port required to attach the debugger may be taken from the
com.sun.bpelse-1.0-2 properties ). 

I suppose that a new user will not be able to use debugger until he reads a
tutorial/manual. This looks like a usability issue for me
Comment 1 Jiri Kopsa 2006-07-26 11:48:24 UTC
This looks like a P1 usability issue to me. Users won't be able to use debugger.
Or there is a workaround?

What are the possible solutions? I expected debugging would just work out of the
box.
Comment 2 Michael Frisino 2006-07-26 12:25:27 UTC
Several points:

1) Alexander can modify the Attach dialog to show default values for host and
port.  

2) Alexander can add a message to the Attach dialog something like:
"Make sure the BPEL Engine Debug Property is enabled".
This is just an idea. Any opinions?

3) I think QE should open a separate bug against JBI Manager if you do not like
the name of the "com.sun.bpelse-1.0-2" node in the Runtime tree. I do not see
this as being a Debug bug per se.

3) Perhaps QE should open a separate bug against JBI Manager to request that the
Debug property value be True for the bundled version installed with IDE. This
would make this whole "set Debug property step" unnecessary. I don't know any
reason why that cannot be default value.


4) I think an RFE should be logged against the JBI Manager to see if they can
add an API so that the Debugger client can programmatically change the runtime
mode from non-debug to debug. This way user will not need to be involved. 

So in summary, I think this bug should be limited to item 1 and the other items
should be separate bugs and rfe.
Comment 3 Jiri Kopsa 2006-07-26 12:59:36 UTC
I agree with #1, #3 and #4. I don't agree with #2. Debugging should just work.
Comment 4 Vladimir Yaroslavskiy 2006-07-27 13:18:27 UTC
Fixed #1: show default values for host and port (localhost and 3343).

For another items, please, file separate bugs.
Comment 5 lchang 2006-08-04 02:50:48 UTC
Issue #1 - this has been fixed.
Issue #2 - this will be resolved with issue #4's solution
Issue #3 - http://www.netbeans.org/issues/show_bug.cgi?id=81897
Issue #4 - http://www.netbeans.org/issues/show_bug.cgi?id=81898

Closing this issue as all issues mentioned above are addressed