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: NetBeans IDE 6.0 (Build 200711261600) VM: Java HotSpot(TM) Client VM, 1.6.0_03-b05 OS: Linux, 2.6.18-53.1.4.el5.centos.plusxen, i386 User Comments:
Created attachment 55357 [details] stacktrace
Created attachment 55372 [details] stacktrace
THIS ISSUE HAS ALREADY 20 DUPLICATES
Build: NetBeans IDE 6.0.1 (Build 200801291616) VM: Java HotSpot(TM) Client VM, 1.6.0_03-b05 OS: Windows XP, 5.1, x86 User Comments:
Created attachment 56385 [details] stacktrace
Created attachment 56767 [details] stacktrace
Build: NetBeans IDE Dev (Build 200802251204) VM: Java HotSpot(TM) Client VM, 1.5.0_13-121 OS: Mac OS X, 10.4.11, i386 User Comments: Entering JavaScript
Created attachment 57227 [details] stacktrace
Build: NetBeans IDE Dev (Build 200802270005) VM: Java HotSpot(TM) Client VM, 1.6.0_03-b05 OS: Windows XP, 5.1, x86 User Comments: 1. Create web application with "JavaServer Faces" framework. 2. Deploy it. 3. Collapse application node in "Projects" window. 4. Create web application with "Struts" framework. 5. Deploy it. 6. Collapse application node in "Projects" window. Result: IllegalArgumentException arises.
Created attachment 57430 [details] stacktrace
Build: NetBeans IDE Dev (Build 20080304063458) VM: Java HotSpot(TM) 64-Bit Server VM, 1.6.0_04-b12-45-optimized OS: Mac OS X, 10.5.2, x86_64 User Comments: Editing HTML file, more precisely, typing '<br>'.
Created attachment 57718 [details] stacktrace
Created attachment 57721 [details] stacktrace
Build: NetBeans IDE Dev (Build 200803170003) VM: Java HotSpot(TM) Client VM, 10.0-b19 OS: Linux, 2.6.24-12-generic, i386 User Comments: I created a Desktop project (with all the default forms), then I created a new package in it and inserted a new JFrame Form. I tried to move forms among the packages (using refactoring), and this exception was thrown when I attempted to move a package back to its "original" package. Internationalizatioin was on.
Created attachment 58485 [details] stacktrace
Build: NetBeans IDE Dev (Build 200803190008) VM: Java HotSpot(TM) Client VM, 10.0-b19, Java(TM) SE Runtime Environment, 1.6.0_04-b12 OS: Linux, 2.6.24-12-generic, i386 User Comments: I deleted a JPanel containing a JButton from a Frame (AWT). I had selected both JPanel and JButton (using Ctrl key). JPanel had set "FlowLayout", Frame had set "AbsoluteLayout".
Created attachment 58667 [details] stacktrace
Build: NetBeans IDE Dev (Build 200803250006) VM: Java HotSpot(TM) Client VM, 1.5.0_13-119, Java(TM) 2 Runtime Environment, Standard Edition, 1.5.0_13-b05-237 OS: Mac OS X, 10.5.2, i386 User Comments: Edited html file qa/www/bugzilla/bug_priority_guidelines.htm and the exception apeared in the exception dialog.
Created attachment 59040 [details] stacktrace
There is sanity check in setSelectedNodes() which checks if nodes that should be selected are under root. If not exception is thrown. In most cases setSelectedNodes() is called directly from Form designer (http://www.netbeans.org/nonav/issues/showattachment.cgi/58485/stacktrace.txt) or gsfret.navigation (http://www.netbeans.org/nonav/issues/showattachment.cgi/59040/stacktrace.txt). It seems you try to setSelectedNodes() which were deleted meanwhile or something similar. Please evaluate.
I have seen this issue several times - always as a consequence of another problem that appeared before. So, there's nothing to fix in form module just because of this exception - the root of the problem must be fixed.
moving opened issues from TM <= 6.1 to TM=Dev
Created attachment 62049 [details] stacktrace
Created attachment 62184 [details] stacktrace
This issue has already 100 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=4511
I'm marking as patch candidate, the issue has 100 duplicates lot of them are from 6.1 Tome, could you look at it? Thank you
As I wrote, I believe the problem is not in explorer - there is just sanity check of supplied nodes. Most of stack traces correspond to existing issue in gsfret.navigation e.g. http://www.netbeans.org/nonav/issues/showattachment.cgi/57227/stacktrace.txt is identical to http://www.netbeans.org/nonav/issues/showattachment.cgi/57281/bug.txt (fixed issue http://www.netbeans.org/issues/show_bug.cgi?id=128452). Some of exceptions arise in form designer, so I think it should be also fixed there.
Reassigning to Form
Reassigning back to openide. I don't see any reason why this mix of problems should reside in form module. Note that this issue will contain more and more duplicates from different sides of NetBeans. It is an unfortunate umbrella for wide set of problems. It is more a problem in exception reporter itself that it creates such a mix. I went through all 100 duplicates: 70x org.netbeans.modules.gsfret.navigation.ClassMemberPanelUI.selectElementNode 15x com.jaspersoft.ireport.designer.JrxmlVisualView.setSelectedNodes 11x org.netbeans.modules.form.ComponentInspector.setSelectedNodes 2x org.netbeans.modules.retouche.navigation.ClassMemberPanelUI.selectElementNode 1x org.netbeans.modules.form.FormDesigner$3.propertyChange 1x org.netbeans.modules.form.ComponentInspector.focusFormImpl Even the group of 11 execeptions from ComponentInspector.setSelectedNodes has probably several reasons. As I wrote already, there is nothing to fix in the form regarding this exception. It is usually caused by another problem (= exception) caused before. Hence, the original problem must be fixed (we do have reports about the original problems and don't need this one). As for the high priority of this issue, it seems that it is mainly about the gsfret.navigation case that should be fixed already.
If I understood correctly this issue is fixed for gsfret.navigation and the form has root issues causing this issue reported. Because most of exception reports are duplicates of already fixed #128452, I am closing it as duplicate of #128452. *** This issue has been marked as a duplicate of 128452 ***
Tomas, I would say this issue can't be duplicate of issue 128452 : issue 128452 was fixed in NB 6.1 codebase, but if you look at reported duplicates, there are duplicates with gsfret.navigation reported after 6.1 release date for builds from May ..... e.g. http://statistics.netbeans.org/analytics/detail.do?id=52566
Created attachment 62606 [details] stacktrace
Tomas, could you please comment Marian's last question? Thanks
If gsfret.navigation issue was reported also for codebase after fix of #128452 I think #128452 should be reopened.
The issue didn't meet nomination criteria for 61patch2 till nomination cut-off date. It has been moved to the next patch.
Reopening #128452... *** This issue has been marked as a duplicate of 128452 ***
This isssue if not duplicate of issue 128452 since there are several modules involved in the incorrect nodes selection. Issue 128452 used to be about gsf navigators before you duplicated another three "garbage" issues to it. It is not a good practice to get rid of issues in this way. I belive filling particular issues to particular modules according to the stacktraces is how it should be done. I do not see any reason why html/editor issue should be used for duplicating visual web, xml multiview or form editor bugs. I'll likely close 128452 as invalid and file new issue to gsf navigation with the proper stacktrace.
Exception reporter mixed here issues from gsfret.navigation (~70 duplicates) and form (~15 duplicates). jstola wrote that the errors causing these form issues are reported for form already. Remaining 70 reported issues _are_ duplicates of #128452. I would expect that this issue should be marked as duplicate of #128452... However, mfukala thinks it is better to file new issue and loose these duplicates. Therefore, I am marking this as invalid.
Wiping 61fixes3-candidate keyword from status whiteboard. Keeping sustaining in Cc: just in case someone would like to do something weird with this INVALID issue. Once you file new issue against gsf navigation please consider adding 61fixes3-candidate keyword to status whiteboard and sustaining to Cc:. Existing trunk-verified changeset is required for patch3 inclusion.