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 32216 - Define communication interface between central unit and persistence
Summary: Define communication interface between central unit and persistence
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: PC All
: P3 blocker (vote)
Assignee: mslama
Depends on:
Blocks: 32211 32212
  Show dependency tree
Reported: 2003-03-24 08:22 UTC by Peter Zavadsky
Modified: 2008-12-23 12:26 UTC (History)
0 users

See Also:
Issue Type: TASK
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Peter Zavadsky 2003-03-24 08:22:38 UTC
The interface will consist of:

1) 2 methods in PersistenceManager (only exposed
part of persistence layer): WindowManagerConfig
        void saveWindowSystem(WindowManagerConfig);

2) 4 methods in WindowManagerImpl, used for
informing the cetnral unit about changes (could be
void modeConfigAdded(ModeConfig)
void modeConfigRemoved(ModeConfig)
void topComponentConfigAdded(TopComponentConfig)
void topComponentConfigRemoved(TopComponentConfig)

3) Define method for retrieving serialized
TopComponent according its ID (used for lazy
loading) in PersistenceManager
TopComponent getTopComponentForID();

4) Define the communication structures. Those are
WindowManagerConfig, ModeConfig,
TopComponentConfig. Those structures correspond to
xml files (.wsmgr (WindowManager data), .wsmode
(Mode data), .wstcref (TopComponent data).

Rules: Persistence part is currently in package 
a) It cannot acces any other window system classes
out of that package except the defined methods in 2) 
b) It cannot propagate any exception (IOException)
informing about some io problems to the central
unit. It should take care about it properly (log
some message) and return just data which are
consistent not the corrupted one.
c) It should also manage removals or repairements
of corrupted files
Comment 1 Peter Zavadsky 2003-03-24 13:21:04 UTC
For current state look into package at classes:


Those are subject to change and their final state will be known after
the final version is closed.
Comment 2 mslama 2003-04-25 11:07:16 UTC