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 15383 - IO exception when making dominant
Summary: IO exception when making dominant
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: Sun SunOS
: P3 blocker (vote)
Assignee: David Simonek
URL:
Keywords:
: 15553 (view as bug list)
Depends on: 12152 15563
Blocks:
  Show dependency tree
 
Reported: 2001-09-12 09:32 UTC by Jan Zajicek
Modified: 2008-12-23 09:43 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
the exception (3.27 KB, text/plain)
2001-09-12 09:33 UTC, Jan Zajicek 		Details
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 Jan Zajicek 2001-09-12 09:32:46 UTC 
Start ide (I was using build #20010912). Open output window if it isn't opened.
Note that explorer is dominant. Restart ide. Now outputwindow is dominant.
Select explorer and go to the Window | Make Dominant. Attached exception will be
thrown.
Comment 1 Jan Zajicek 2001-09-12 09:33:26 UTC 
Created attachment 2508 [details]
the exception
Comment 2 David Simonek 2001-09-13 17:58:54 UTC 
Yes, caused by the fact that output refuses to be serialized and uses
"writeReplace to null" technique, which now can't be used. Solution
will be to add some support into TopComponent, which will say if
component wants to be serialized at all and how.
Comment 3 Jan Pokorsky 2001-09-17 17:47:46 UTC 
*** Issue 15553 has been marked as a duplicate of this issue. ***
Comment 4 dmladek 2001-09-18 08:00:04 UTC 
CC'ing myself
Comment 5 David Simonek 2001-09-19 13:01:15 UTC 
fixed in main trunk. Will be visible in tomorrow's build.
Comment 6 Jan Zajicek 2001-09-20 14:17:21 UTC 
dev#20010920
Comment 7 Quality Engineering 2003-07-01 16:30:30 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.