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 10993 - [windows]Second (and next) start.
Summary: [windows]Second (and next) start.
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: Sun Solaris
: P1 blocker (vote)
Assignee: mslama
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-04-03 15:52 UTC by Jan Lahoda
Modified: 2008-12-22 23:38 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
First second start exception. (2.44 KB, text/plain)
2001-04-03 15:53 UTC, Jan Lahoda 		Details
Second exception. (2.46 KB, text/plain)
2001-04-03 15:55 UTC, Jan Lahoda 		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 Lahoda 2001-04-03 15:52:24 UTC 
There were two more exceptions while second start (and next, ...). There is no
explorer in no workspace. The second exception fires quite often (aproximatelly
5 times while the start).
Comment 1 Jan Lahoda 2001-04-03 15:53:13 UTC 
Created attachment 972 [details]
First second start exception.
Comment 2 Jan Lahoda 2001-04-03 15:55:31 UTC 
Created attachment 973 [details]
Second exception.
Comment 3 David Simonek 2001-04-04 14:12:38 UTC 
I cannto reproduce it... which build? which jdk? Please, be so kind and try to
help me a bit....thanks.
Comment 4 Jan Lahoda 2001-04-05 11:02:27 UTC 
Sorry, it is JDK1.2.2 and MDI. Build was release32 19.
Comment 5 David Simonek 2001-04-06 08:27:32 UTC 
Reassigning to Marek. Hint: try to look in DefaultCreator, it seems that it's
trying to install default window system layout not only during first start, but
also during second and next, which is wrong.
Comment 6 Jaroslav Tulach 2001-04-06 09:21:26 UTC 
Jesse, what the ant module is trying to do?
Comment 7 mslama 2001-04-06 14:21:44 UTC 
Problem was with deserialization in JDK 1.2.2: Method method
ObjectStreamClass.getField() returns always null (It works fine in 1.3.0.)
Method ObjectStreamClass.getFields() returns correct array so we use getFields()
instead of getField() to check presence of field with given name.New method
hasObjectStreamField added to org.netbeans.core.windows.util.WindowUtils.

Calls of getField() was eliminated in
org.netbeans.core.windows.WindowManagerImpl
org.netbeans.core.windows.WorkspaceImpl
org.netbeans.core.windows.frames.SplitContainerImpl.

I tested it on Linux RH 6.2 (JDK 1.2.2 and 1.3.0), need to be verified on
Solaris and Win2000. Behaviour was the same both for SDI and MDI.
Comment 8 Jan Lahoda 2001-04-09 09:59:47 UTC 
It looks fixed in release 3.2, build 23.
Comment 9 Jan Chalupa 2001-05-05 20:50:33 UTC 
Target milestone 3.2
Comment 10 Quality Engineering 2003-07-01 16:46:11 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.