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 85699 - Create New Port/Operation dialogs -- disabled message parts tables are misleading
Summary: Create New Port/Operation dialogs -- disabled message parts tables are mislea...
Status: RESOLVED WONTFIX
Alias: None
Product: xml
Classification: Unclassified
Component: WSDL Tools (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Shivanand Kini
URL:
Keywords:
: 129406 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-09-25 16:44 UTC by jlautz
Modified: 2016-07-07 09:57 UTC (History)
2 users (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 jlautz 2006-09-25 16:44:33 UTC
Seen on Windows XP with NB 55 060923 and JDK 1.5.0_07:

This is probably a usability enhancement at this point:

1. Open/create a valid WSDL document.
2. Click Port Types, open the contect menu, and click Add -> Port Type.
3. Choose an existing message definition for the Input message type.
==> The message parts table is disabled, but it still contains the default
content for creating a new message type. 

I (and I will suggest, a typical user), would expect the message parts table
contents to reflect the info for the selected message type, while appearing
disabled to indicate that the definition cannot be changed.

I found it rather confusing to have the message parts table be both static and
wrong for the current selection in the associated Input/Output/Fault field.
Random thoughts: "didn't I define the message type properly? I don't remember
which message I want to use, and I can't see the content in this dialog, so I
need to cancel out and look around and come back."
Comment 1 Shivanand Kini 2006-09-25 20:38:13 UTC
Changing this as to a enhancement.
Comment 2 Shivanand Kini 2008-03-06 18:34:32 UTC
*** Issue 129406 has been marked as a duplicate of this issue. ***
Comment 3 Kirill Sorokin 2008-03-06 19:41:31 UTC
Yet the issue is a defect -- this IS misleading.
Comment 4 Martin Balin 2016-07-07 09:57:05 UTC
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue.

Thanks for your cooperation,
NetBeans IDE 8.2 Release Boss