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 13043 - Serialized information about loaders inconsistent after autoupdate
Summary: Serialized information about loaders inconsistent after autoupdate
Status: VERIFIED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: Vitezslav Stejskal
URL:
Keywords:
Depends on:
Blocks: 30722
  Show dependency tree
 
Reported: 2001-06-20 18:46 UTC by Petr Jiricka
Modified: 2008-12-22 15:55 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 Petr Jiricka 2001-06-20 18:46:20 UTC 
See also bugtraq bug 4463066.

After Autoupdate, the updated restarts the IDE. New modules are installed and 
the IDE updates the installedmodules.xml file. The modules may also update the 
IDE Global Options, they may for example add new loaders and specify order of 
these loaders relative to other loaders. However, this information is not saved 
until the IDE is closed.

So when the IDE is closed forcibly, this information is 'out of sync' with the 
installedmodules.xml.

When the IDE starts the next time, the order of loaders may not respect the 
relative constraints provided by module.
Comment 1 Vitezslav Stejskal 2001-09-21 13:05:28 UTC 
Moving to projects.
Comment 2 Vitezslav Stejskal 2001-09-21 14:01:57 UTC 
Anybody solving this, please see issue #8958 as well.
Comment 3 Vitezslav Stejskal 2001-11-22 16:42:08 UTC 
We are going to reimplement Data Loaders subsystem to be more extensible and declarative, new storage 
should fulfill requirement from this issue. Please, see the progress of issue #16389.

*** This issue has been marked as a duplicate of 16389 ***
Comment 4 Jesse Glick 2003-01-07 15:07:14 UTC 
This is no duplicate, though it may be blocked by another issue.
Comment 5 Jesse Glick 2003-01-07 15:09:26 UTC 
In fact such problems should be fixed by now (at least for 4.0,
possibly for 3.4 too). All loaders are stored to loaders.ser and
relative constraints in the loader pool are always checked at startup.
 Reopen if you have any reason to believe otherwise.

Note that loader storage is done entirely by core at the moment;
projects module is not involved.
Comment 6 Petr Jiricka 2003-07-09 16:47:48 UTC 
Verified.