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 51168 - Flickering nodes of appserver in server registry
Summary: Flickering nodes of appserver in server registry
Status: RESOLVED INVALID
Alias: None
Product: javaee
Classification: Unclassified
Component: Code (show other bugs)
Version: 4.x
Hardware: PC All
: P4 blocker (vote)
Assignee: Nitya Doraisamy
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2004-11-04 16:33 UTC by _ rkubacki
Modified: 2008-09-17 12:08 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description _ rkubacki 2004-11-04 16:33:44 UTC 
NB4.1EA1 + Sun appserver, JDK 1.5.0, Linux, P4
2GHz/1GB.

When I browse the content of server registry in
runtime tab I see flickering for each subnode node
of Applications node. The IDE quickly realizes
that there is no application of given type when I
expand a node but the please wait node is set even
faster so the tree growths and shrinks its size.
Comment 1 Nitya Doraisamy 2005-02-18 02:02:42 UTC 
The runtime tree sets the please wait node while it is issuing calls
and waiting for server response. In cases where server returns an
empty list, flickering happens. Can be fixed by allowing the server
some default time to respond before setting the wait node.
Comment 2 _ ludo 2005-03-17 05:59:10 UTC 
Not a p3 imo.
The ui is showing a wait node, then the real content very fast after that.
Not really visible on my laptop.
Comment 3 Petr Blaha 2006-03-13 13:47:36 UTC 
TM 5.0 -> TBD
Comment 4 pslechta 2008-09-17 12:08:49 UTC 
This is not a bug IMHO. It is good strategy to show wait node, because you never know how fast is your machine, how fast
is server's reply (in case of remote server it depends on network speed), etc.

It is not a big problem if user with fast machine sees this node for a while and then the node is changed to empty node.

Closing as INVALID. Reporter, you may reopen, but I really think that this is not a problem.