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.1 (Build 201112071828) VM: Java HotSpot(TM) Client VM, 22.0-b10, Java(TM) SE Runtime Environment, 1.7.0_02-b13 OS: Linux User Comments: aldobrucale: Clicked on the "Design" button for a swing component, there probably was an exception in my own code while I was modifying it. Stacktrace: java.lang.NullPointerException at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:187) at com.google.common.cache.LocalCache.get(LocalCache.java:3966) at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3971) at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4831) at com.google.common.cache.LocalCache$LocalManualCache.getUnchecked(LocalCache.java:4836) at com.imavis.omc.deviceui.view.api.CommercialInfo.getCommercialDescription(CommercialInfo.java:36)
Created attachment 115180 [details] stacktrace
not a bug in netbeans code
The exception is in the user code, but the ide was not painted correctly after this happened, and became unusable. IMO the nb code should be resistant to exceptions when it calls user code, catching them earlier in the stack trace.
GUI Builder cannot be resistant against all failures of user component. Not even in theory. For example, the attached exception comes from addNotify() method of the user component. Note that there don't have to be any GUI Builder's code on the stack when this method is called. Hence, the GUI Builder has no way to catch it.