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 9751 - Children.Keys - empty list of children
Summary: Children.Keys - empty list of children
Status: VERIFIED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: All All
: P1 blocker (vote)
Assignee: Jaroslav Tulach
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-02-21 16:42 UTC by _ ttran
Modified: 2008-12-22 21:40 UTC (History)
0 users

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 _ ttran 2001-02-21 16:42:50 UTC
there is a serious regression between dev/130 and dev/131.  The problem shows up
in the component inspector (CI).  CI uses an explorer to display AWT hierarchy.
Each AWT component is presented by a RADComponentNode which uses RADChildren, a
subclass of Children.Keys to implements the list of AWT child components.
The special thing about CI is that it calls node.getChildren().getNodes() quite
early to enforce creation of subnodes.  What's wrong now?

- create a new form
- add panel1, panel2 and panel3 into that form, also add some components to each
 of these panels.
- we would have such a hierarchy
     panel1
        label1
        textfield1
     panel2
        label2
        textfield2
     panel3
        label3
        textfield3
- save this new form
- now try to open the above form using build dev/131.  Go to CI, expand panel1,
 panel2, panel3.  You see only panel3 is okay, panel1 and panel2 have no
  children
- if you go to the form window and do something with it, uncaught exceptions  
  will start flying on the screen

This is a regression caused by the change in Children.java between rev 1.83 and
rev 1.84.

---------------
revision 1.84
date: 2001/02/20 11:11:56;  author: jtulach;  state: Exp;  lines: +29 -22
Children.Keys are smaller, one instance field has been removed and replaced by
static ThreadLocal variable. The functionality is the same
---------
Comment 1 Jesse Glick 2001-02-21 17:40:38 UTC
Trung, if you know this change caused the bug, maybe for the short term roll it
back until we can investigate it better.
Comment 2 Jaroslav Tulach 2001-02-21 18:23:48 UTC
Fixed.
Comment 3 Marian Mirilovic 2003-09-05 16:03:56 UTC
old issue - verified