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.

Bug 12131 - FORTE:Closing output window throws exception
Summary: FORTE:Closing output window throws exception
Status: CLOSED WORKSFORME
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: Sun Solaris
: P2 blocker (vote)
Assignee: anovak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-05-11 21:32 UTC by pcmreddy
Modified: 2008-12-23 11:23 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description pcmreddy 2001-05-11 21:32:34 UTC 
Create a servlet, and compile it.
This opens the output window.
Close this window by double clicking at Top left button.
This throws following exception.

Thu May 10 11:11:42 PDT 2001: java.lang.NullPointerException:
null
java.lang.NullPointerException
        at
org.netbeans.core.output.OutPane.clearLineTable(OutPane.java:207)
        at
org.netbeans.core.output.OutPane$PaneWriter.reset(OutPane.java:457)
        at
org.netbeans.core.output.OutPane$PaneWriter.close(OutPane.java:453)
        at
org.netbeans.core.output.OutputTab.closeInputOutput(OutputTab.java:334)
        at
org.netbeans.core.output.OutputTab.topComponentClosed(OutputTab.java:263)
        at
org.netbeans.core.windows.WindowManagerImpl$TopComponentManager.doClose(WindowManagerImpl.java:1192)
        at
org.netbeans.core.windows.WindowManagerImpl$TopComponentManager.close(WindowManagerImpl.java:1138)
        at
org.openide.windows.TopComponent.close(TopComponent.java:252)
        at
org.openide.windows.TopComponent.close(TopComponent.java:223)
        at
org.netbeans.core.windows.ModeImpl.frameClosing(ModeImpl.java:743)
        at
org.netbeans.core.windows.frames.WindowFrameListenerAdapter.windowClosing(WindowFrameListenerAdapter.java:60)
        at
java.awt.AWTEventMulticaster.windowClosing(AWTEventMulticaster.java:291)
        at
java.awt.AWTEventMulticaster.windowClosing(AWTEventMulticaster.java:290)
        at
java.awt.Window.processWindowEvent(Window.java:798)
        at
javax.swing.JFrame.processWindowEvent(JFrame.java:241)
        at java.awt.Window.processEvent(Window.java:774)
        at
java.awt.Component.dispatchEventImpl(Component.java:2593)
[catch] at
java.awt.Container.dispatchEventImpl(Container.java:1214)
        at java.awt.Window.dispatchEventImpl(Window.java:912)
        at
java.awt.Component.dispatchEvent(Component.java:2497)
        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)
Comment 1 Jan Zajicek 2001-05-16 12:25:56 UTC 
assigning
Comment 2 anovak 2001-08-22 10:22:58 UTC 
I think that there already was a similar bug that I fixed a time ago.
I do not remember number, however. I remember the fix and it is
present in main trunk, so I am closing this as "cannot reproduce".
Comment 3 Quality Engineering 2003-07-01 16:05:14 UTC 
Resolved for 3.4.x or earlier, no new info since then -> verified.
Comment 4 Quality Engineering 2003-07-01 16:41:12 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.