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.
build 20070806 Open a visual MIDlet file a last week build, the navigator nodes are mix it up see picture. and the follow exception appears.
Created attachment 46202 [details] Navigator
Created attachment 46203 [details] IndexOutOfBoundsException
Created attachment 46205 [details] Right- IndexOutOfBoundsException
The first attachment (46203.txt) doesn't belong to this issue it was wrong sorry =)..!!!!
It looks like this IOBE is not related to the wrongly painted navigator (directly). It is related to the graph libraries. David take a look at it.
It looks like netbeans bug, not related directly to the Inspector. Do you know how to reproduce it?
Actually this is JDK issue. It may be caused by updating a TreeModel outside of AWT-thread.
I was looking around inet and found out that this exception is caused by a race-condition within the implementation of TreeModel of a JTree that is in the navigator. Karol, could you look at the model implementation? Is the tree-model provided and handled by us?
Could you provide link to the information about this bug? Implementation of navigator doesn't touch TreeModel at all, everything is done underneath inside of BeanTreeView and implementation of NodeTreeView which is just extended DefaultTreeModel. Thats way I suggested that probably it is NB problem. Anyway do we have steps to reproduce it?, if it possible to reproduce it we can easily fix (if it is not a VM problem).
Reassigning to openide/awt module. Could you look at it? Thanks.
Passing back to dkaspar, this has nothing to do with core team. Very sorry, but I can't and won't evaluate all exceptions that ends in Swing code. Likely that error is on the JDK side, so please try to search bugster database for mentioned exception or try to reproduce the exception somehow. Sorry for not much help, but I know even less then you do here...
Info: Google for: ArrayIndexOutOfBoundsException VariableHeightLayoutCache$TreeStateNode.collapse You will get a few answers all of them looks like that the issue is a race condition during tree-model modification.
Unfortunately so far I was not able to reproduce it. Probably this bug is caused by updating tree model outside of AWT thread. I check my code for possible NOT-AWT structure nodes method calls and I it looks safe. Since I was not able to gather enough information about this problem + no know steps to reproduce it I'm marking this issue as a INCOMPLETE.