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 7.0 (Build 201104080000) VM: Java HotSpot(TM) Client VM, 19.1-b02, Java(TM) SE Runtime Environment, 1.6.0_24-b07 OS: Windows XP User Comments: javydreamercsw: Trying to rename top component Stacktrace: java.lang.UnsupportedOperationException: XXX: AlwaysEnabledAction[null] at org.netbeans.modules.apisupport.project.layers.WritableXMLFileSystem.writeAttribute(WritableXMLFileSystem.java:900) at org.openide.filesystems.AbstractFileObject.setAttribute(AbstractFileObject.java:357) at org.openide.filesystems.AbstractFileObject.setAttribute(AbstractFileObject.java:340) at org.openide.filesystems.MultiFileObject.copyAttrs(MultiFileObject.java:1568) at org.openide.filesystems.MultiFileObject.copyContent(MultiFileObject.java:1531) at org.openide.filesystems.MultiFileObject.rename(MultiFileObject.java:1235)
Created attachment 108157 [details] stacktrace
Not sure how to reproduce. Tried creating a new TopComponent in both 7.0 - using @TopComponent.Registration - and 6.9 - using XML layer entries; and used rename refactoring to change the class name. No error in either case. (Only in 7.0 will the refactoring really work, since the annotations carry over into the new source file.) Probably all of the mutating refactoring plugins in apisupport.refactoring (i.e. everything other than the Find Usages plugin and the editor hints) should just be deleted, as they have never been reliable. Too big of a change for 7.0.1. Using "raw:" attribute names might avoid this exception. Without a way to reproduce it, though, it is difficult to be sure. *** This bug has been marked as a duplicate of bug 196608 ***