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 55052 - Always show all container nodes
Summary: Always show all container nodes
Status: RESOLVED FIXED
Alias: None
Product: webservices
Classification: Unclassified
Component: Code (show other bugs)
Version: 4.x
Hardware: PC All
: P4 blocker (vote)
Assignee: issues@webservices
URL:
Keywords:
: 52926 53007 69431 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-02-16 14:00 UTC by L Martinek
Modified: 2008-09-17 19:24 UTC (History)
5 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 L Martinek 2005-02-16 14:00:48 UTC
Nodes 'Web Services' and 'Web Service References'
should be displayed only if they contain subnodes.
Now project contains too many subnodes (e.g. 9 for
me) and it's confusing.
Comment 1 Martin Grebac 2005-02-16 14:09:52 UTC
I don't think we should remove the nodes. They actually advertise the
functionality, and I don't find them confusing. Leave to UI to decide.
Comment 2 Vince Kraemer 2005-02-16 14:42:00 UTC
Having nodes appear/disappear is pretty confusing.  It is similar to having menu items 
that change state.  People loose track of "why" something enables, then become frustrated 
when they cannot get an item to activate.

That said, the current Nodes have some serious issues.

1. There is no menu item to create a web service on the "Web Services" node.  Since you 
CAN create a WS from the project's New item in the CSM, it would be nice to have a 
"limited New" on the node, that just allows you to create a Web Service.
2. The "Web Service References" node doesn't appear initially when a web or ejb project is 
created.  They appear once the user creates one from the project's New menu (I guess).  So 
we are mixing the two strategies.  That is even nmore confusing.
Comment 3 L Martinek 2005-02-16 15:43:40 UTC
Because there isn't New menu item on Web Services node so user can't
use this node to create new file I thouht this node was "useless" when
there  was no web service. Having New menu item on this node would be
great.
Comment 4 _ pcw 2005-02-17 04:06:37 UTC
Personally, I'd prefer that the nodes not be present unless there are
services (or clients) respectively.  But HIE has consistently ruled
against this and in fact, there is a bug filed against the web service
reference node because it does in fact only show up if you have
clients in the project.

As for providing access to <New> from the web service node, this can
be done easily (1 line?) (I think the web service reference node
offers this - at least it did last fall).  But we are way past UI
freeze so I think that will not happen for 4.1 w/o escalating and I
don't think this is worth the energy (I agree it should be there though.)
Comment 5 jrojcek 2005-02-17 12:26:41 UTC
I tend to say that the web service parent nodes should be always shown. Consider this: if 
the user removes the last web service, should the parent node disappear?

The new menu should be available on this node and it should contain all the new items 
defined for project. We had a discussion before 4.0 whether to hide/show new items the 
user can/cannot create in a certain container and we agreed that we will do it only at the 
project level. So, all New menus in the project show the same list of recently used new 
items.
Comment 6 Jiri Kopsa 2005-03-18 22:16:10 UTC
The presence of container nodes has been discussed widely in this issue, as well
as in #52926 and #53007. There is also related issue regarding the context menus
of these nodes (now filled as #56662)

Related issue:
56662 Context menu on the project explorer out of UI spec
http://www.netbeans.org/issues/show_bug.cgi?id=56662

Duplicate issues:
52926 Confusing UI around Sun Resources templates
http://www.netbeans.org/issues/show_bug.cgi?id=52926

53007 Different project view for webapps with/without webservices 
http://www.netbeans.org/issues/show_bug.cgi?id=53007

The conclusion is that:
- all container nodes should be always shown
- the "New File" context menus should contain a project-wide set of items + history
- a discussion about the contextuality of the "New File" context menu will be
restarted for promo f

The context menus are solved in #56662, the presence of nodes is solved in this
issue.

So, what needs to be repaired (in this issue):

1. Web Service Clients node does not appear by default (but it should)
Note: It was renamed from Web Service References - see current UI spec: 
http://web.netbeans.org/nonav/doc/webapp-project-ui-spec-promoe.html#Project_Window

2. Server Resources node does not appear by default in both Web Application
project as well as in EJB Module project (but it should)

Assigning to Andrei (to fix the EJB module). Andrei, please reassign the
responsible person (regarding the Web Application) if necessary. Hopefully I've
added them all (Radko) on the CC.
Comment 7 Jiri Kopsa 2005-03-18 22:17:34 UTC
*** Issue 53007 has been marked as a duplicate of this issue. ***
Comment 8 Jiri Kopsa 2005-03-18 22:19:06 UTC
*** Issue 52926 has been marked as a duplicate of this issue. ***
Comment 9 Andrei Badea 2005-03-25 10:21:43 UTC
The Server Resources node has been fixed, the commit log is in issue #56662.
Comment 10 Andrei Badea 2005-03-29 13:08:37 UTC
Peter: to summarize: UI says the Web Service Clients node should be always
visible in the web project. I think you are the proper person to ask, could you
look at it? Or close if you feel this can't be done for 4.1.
Comment 11 _ pcw 2005-10-01 01:05:35 UTC
Reassigning to websvc since I am not working in this area anymore.
Comment 12 Lukas Jungmann 2005-11-29 16:54:19 UTC
*** Issue 69431 has been marked as a duplicate of this issue. ***
Comment 13 Lukas Jungmann 2008-09-17 19:24:04 UTC
this is already solved, AFAICT