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 33282 - Problem with cleaning of TopComponents
Summary: Problem with cleaning of TopComponents
Status: VERIFIED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: mslama
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-28 16:28 UTC by mslama
Modified: 2008-12-23 09:34 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 mslama 2003-04-28 16:28:21 UTC 
It seems it is necessary due to disabling/enabling
modules. Now folder is only one but when module is
disabled its top component settings file stays in
local filesystem (if it is already stored there)
and when module is enabled top component is
deserialized from settings file whcih stayed on
local layer not from file on module layer. So it
is necessary somehow delete top component settings
files of disabled modules somehow. One way is to
separate file stored locally to different folder.
Another way could be to use event from
InstanceDataObject to delete settings file on
local layer. Need to investigate.
Comment 1 mslama 2003-04-28 16:38:20 UTC 
Steps to reproduce problem:
1.Start IDE with empty user dir.
2.Exit IDE. (TopComponent's settings files are stored.)
3.Start IDE.
4.Disable and enable projects module.
5.You can see empty Projects tab - no title, empty node.

If you do the same withoutsteps 1,2 you will see projects tab with
title "Projects" and root node "No project is open..."
Comment 2 mslama 2003-04-29 15:05:39 UTC 
It is not clear what is wrong. Definitely when there is localy
project.settings file PROP_COOKIE event does not come to
PersistenceManager (though it works in main trunk in current dev build
200304290100) -> it is not clear if it will solve problem or not if
event will come and TopComponent cache in PersistenceManager will be
cleared. See issue #31478.

I change it to DEFECT and keep it open to check it on branch. The same
scenario as above works fine on dev build 200304290100.
Comment 3 Marian Mirilovic 2003-11-26 12:56:00 UTC 
Because Window System v1 will not be supported from now by our team, all old
winsys issues (now "core/window system v1" issues) are going to be closed as
WONTFIX. 

Changes in API which emerged both from UI spec 
and problems with adjusting to the older API are described in the document
http://core.netbeans.org/windowsystem/changes.html.
 It shows also recommends how the client code should be adjusted to the new
window system.

If you think this issue apply also to the new winsys then change the
subcomponent (to "core/window system") and REOPEN it.
Comment 4 Marian Mirilovic 2004-02-27 14:12:53 UTC 
issue doesn't apply to new window system - verified