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.
Summary: | exception when disabling/enabling projects module | ||
---|---|---|---|
Product: | platform | Reporter: | Pavel Buzek <pbuzek> |
Component: | Data Systems | Assignee: | Vitezslav Stejskal <vstejskal> |
Status: | CLOSED DUPLICATE | ||
Severity: | blocker | ||
Priority: | P2 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Windows 3.1/NT | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | 12048 | ||
Bug Blocks: | |||
Attachments: | stack trace |
Description
Pavel Buzek
2001-07-19 11:08:37 UTC
Created attachment 1916 [details]
stack trace
taking this I observed a little bit different behaviour - if I disable and immediatly enable projects module, all works fine for me. But if I disable it, then I try right-click on project in explorer, I got the same message as in attachement. Then there is problem to re-enable module again. This is not a projects bug, similar thing happens with other data objects too (e.g. java). When a module is unistalled, DataObjects that were recognized by that module are recognized by another loader, but DataShadow still points to the old data object. *** Issue 13752 has been marked as a duplicate of this issue. *** The problem seems to be in DataShadow. It does not update itself when its getOriginal is invalidated (isValid => false). I've changed to code to listen to it (in my temporary directory), but that is still not enough, because the FolderChildren will not update icon for the DataShadow because it uses (primaryfile, loader) as a key and it does not change. Maybe the best solution is to wait for FilterNode.setOriginal and update just the node of the DataShadow. The behavior of DataShadow is same as in previous versions, this problem is surely annoying, but doesn't cause critical troubles (IDE is still usable, no data loss). Lowering priority to P2. If you seem it really critical, please increase prio again. Moving to data systems. As Yarda pointed out this problem is originally caused by poor implementation of DataShadow, thus marking as duplicate. In fact, the problem related particulary to projects module was solved in that module (see bunch of bugs #14291, #13536, #16086). *** This issue has been marked as a duplicate of 11156 *** Resolved for 3.4.x or earlier, no new info since then -> verified Resolved for 3.4.x or earlier, no new info since then -> closing. |