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 32217 - Provide reading of older xml data in persistence
Summary: Provide reading of older xml data in persistence
Status: RESOLVED DUPLICATE of bug 36138
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: 32212
  Show dependency tree
 
Reported: 2003-03-24 08:30 UTC by Peter Zavadsky
Modified: 2008-12-23 12:26 UTC (History)
4 users (show)

See Also:
Issue Type: TASK
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Zavadsky 2003-03-24 08:30:11 UTC
There is necessary to provide reading of older xml
format and also its appropriate conversion to new
config structures (see issue #32216)
Comment 1 Peter Zavadsky 2003-03-24 08:31:51 UTC
Note: reaing of the oldest format (serialized one) whill be not
supported. In that case, default configuration will be used.
Comment 2 mslama 2003-05-07 13:13:49 UTC
Is there any spec how import of old configuration (projects) will be
performed?

We discussed what will be imported from older winsys configuration: To
avoid breaking of new default layout we decided to load only editor
components from old Editing workspace and put them to default place in
new editor area. The problem with this approach is that I must
instantiate all TopComponents from all modes in Editing workspace to
find if it is editor or not. (Probably instanceof CloneableEditor.)
Alternative is to check only TopComponents from mode "editor".

Opinion from projects group: It has no sense to import anything at all
because every source opened in editor must be member of some new
existing project. However such dependency is undefined in case of import.

Still it is possible to import something from point of view of winsys.
The question is if it has any sense in context of IDE.

Is there any usecase when we need to import old winsys configuration
(or part of it) to new winsys?

As mentioned above we will not support import of previous serialized
winsys configuration.
Comment 3 mslama 2003-11-04 16:57:35 UTC
Import of old configuration XML data is implemented in task #36138.

*** This issue has been marked as a duplicate of 36138 ***