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: | Attaching debugger has usability problems | ||
---|---|---|---|
Product: | soa | Reporter: | Mikhail Kondratyev <mikk> |
Component: | BPEL Debugger | Assignee: | Vladimir Yaroslavskiy <yaroslavskiy> |
Status: | CLOSED FIXED | ||
Severity: | blocker | CC: | jkopsa |
Priority: | P2 | ||
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Mikhail Kondratyev
2006-07-26 10:31:08 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. 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. I agree with #1, #3 and #4. I don't agree with #2. Debugging should just work. Fixed #1: show default values for host and port (localhost and 3343). For another items, please, file separate bugs. 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 |