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.
[dev 8th Feb 2000] While deleting GUI Editing workspace by clicking on its tab and selecting Delete. Thu Feb 08 16:45:57 GMT+01:00 2001java.lang.NullPointerException: null java.lang.NullPointerException at org.netbeans.core.windows.frames.SplittedContainerImpl.componentRemoved(SplittedContainerImpl.java:293) at org.netbeans.core.windows.frames.DefaultContainerImpl.removeTopComponent(DefaultContainerImpl.java:274) at org.netbeans.core.windows.ModeImpl$2.performCommand(ModeImpl.java:306) at org.netbeans.core.windows.DeferredPerformer.processCommand(DeferredPerformer.java:145) at org.netbeans.core.windows.DeferredPerformer.putRequest(DeferredPerformer.java:82) at org.netbeans.core.windows.ModeImpl.close(ModeImpl.java:300) at org.netbeans.core.windows.WindowManagerImpl$TopComponentManager.doClose(WindowManagerImpl.java:1183) at org.netbeans.core.windows.WindowManagerImpl$TopComponentManager.close(WindowManagerImpl.java:1130) at org.openide.windows.TopComponent.close(TopComponent.java:252) at org.netbeans.core.windows.ModeImpl.close(ModeImpl.java:343) at org.netbeans.core.windows.WorkspaceImpl.remove(WorkspaceImpl.java:393) at org.netbeans.core.windows.WorkspaceSwitcher$5.actionPerformed(WorkspaceSwitcher.java:159) at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1450) at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1504) at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:378) at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:250) at javax.swing.AbstractButton.doClick(AbstractButton.java:279) [catch] at javax.swing.plaf.basic.BasicMenuItemUI$MouseInputHandler.mouseReleased(BasicMenuItemUI.java:886) at java.awt.Component.processMouseEvent(Component.java:3717) at java.awt.Component.processEvent(Component.java:3546) at java.awt.Container.processEvent(Container.java:1164) at java.awt.Component.dispatchEventImpl(Component.java:2595) at java.awt.Container.dispatchEventImpl(Container.java:1213) at java.awt.Component.dispatchEvent(Component.java:2499) at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:2451) at java.awt.LightweightDispatcher.processMouseEvent(Container.java:2216) at java.awt.LightweightDispatcher.dispatchEvent(Container.java:2125) at java.awt.Container.dispatchEventImpl(Container.java:1200) at java.awt.Window.dispatchEventImpl(Window.java:912) at java.awt.Component.dispatchEvent(Component.java:2499) at java.awt.EventQueue.dispatchEvent(EventQueue.java:333) at java.awt.EventDispatchThread.pumpOneEvent(EventDispatchThread.java:103) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93) at java.awt.EventDispatchThread.run(EventDispatchThread.java:84)
Reassigning to Marek Slama, my favourite co-worker :-)
Fixed in SplittedContainerImpl.componentRemoved. Commented premature call of closeTabbedContainer() - it happened only when workspace was not active eg. when workspace was deleted.
[NetBeans 3.2 build #8] verified
Occured again in build 20010328-1315_IE while deleting a component in Form editor. Wed Mar 28 14:43:09 CEST 2001: java.lang.NullPointerException: null java.lang.NullPointerException at org.netbeans.core.windows.frames.SplittedContainerImpl.componentNameChanged(SplittedContainerImpl.java:408) [catch] at org.netbeans.core.windows.frames.DefaultContainerImpl$DoPropertyChange.run(DefaultContainerImpl.java:759) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:154) at java.awt.EventQueue.dispatchEvent(EventQueue.java:337) at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:131) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:98) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93) at java.awt.EventDispatchThread.run(EventDispatchThread.java:85)
Huh, it seems that there is some misunderstanding, because the exception Jiri is reporting is different from original one and it occured in different situation. Why didn't you create new bug, Jiri? Please do so, and attach set of steps to reproduce the problem. Without reproduction, issue is invalid because I will not be able to do anything with it. Thanx.
You are right.
Resolved for 3.4.x or earlier, no new info since then -> closing.