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.
JDK1.5.0, Solaris, dev build March 22, 2005 The folder instance containing nodes of runtime tab is initialized during shutdown. This slows down the whole action (it takes ~0.5 sec on my Solaris 10 running on ULTRA 60) as it loads new classes and does a lot of unneceseary processing to create nodes like: database explorer root node, HTTP server node, XML catalog node and others. I am not sure what triggers this processing as it is runnable in RP - FolderInstance$ChildrenRefreshRunnnable. Maybe it is related to storing of runtime tab as a part of winsys.
Now I see that this is caused by DatabaseModule.close(). It should be more friendly and do nothing if there is no connection. Split of nodes and underlying data can help here.
I hope this issue is fixed now. After integrating the Database Explorer API DatabaseModule.close() doesn't do anything with the Runtime tab when it retrieves the list of connections. But note that if a connection was connected, calling disconnect() would still initialize the Runtime tab.
VERIFIED