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.
Some change (probably in nodes or explorer) between NB 3.4.1 and 3.5 affects behaviour of the Database Explorer module. Scenario: 1. Start the IDE. 2. Create database connection in the Database Explorer. Connection node will appear under the Databases node on the Runtime tab. 3. Enable any disabled module. 4. Try to create another database connection. Conection will not appear under the Databases node. It will be displayed after the restart of the IDE. The problem is that the connection and its node are created but not displayed. If I use the same version of the Database Explorer in NB 3.4.1 it works, if I use it with dev build it doesn't work. The code is the same but the behaviour is different, that's why I think it was caused by any openide change. If you are aware of any openide change which I should reflect in my code, let me know, please. ----------------------------------------------------- Bug transferred into Issuezilla, original report : http://developer.java.sun.com/developer/bugParade/bugs/4824404.html
reassigned to nodes subcomponent for evaluation.
I'm sorry I don't think this is bug in nodes. Could you please provide some debug info or test case e.g. which property is fired and not reflected in the explorer etc.
It seems the bug was caused by changes in org.openide.nodes.ChildrenArray class between revisions 1.8 and 1.9. Method isInitialized() returns different values between these revisions. Is looks like ChildrenArray lost the associated nodes. I will implement a workaround for Database Explorer module to prevent this behaviour until the real source of the problem is fixed. New issue against openide/nodes will be filed.
Changing the milestone to NB35, it needs to be fixed for this release, at least as a workaround in Database Explorer module.
Workaround implemented.
I am reopening this bug because 4824404 is not fixed and was closed as a dup of this bug. Corporate policy is such that bug 4824404 cannot be reopened when closed as a duplicate. My understanding is the EE development wants a fix implemented in Netbeans and is not willing to do a workaround.
Closing. The right issue for the described bug is #31658. Track that issue for the progress.
VERIFIED