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 after deactivation | ||
---|---|---|---|
Product: | platform | Reporter: | novakm <novakm> |
Component: | Module System | Assignee: | Jesse Glick <jglick> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | CC: | jrechtacek |
Priority: | P4 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | Exception Stacktrace |
Description
novakm
2007-09-06 09:20:06 UTC
Created attachment 48232 [details]
Exception Stacktrace
reassigning for evaluation I don't know how can I affect exceptions after deactivation of our modules. When the modules provide DataLoaders, EditorKits, etc... many references remain in the running IDE and many exceptions are thrown then. Is there any way how to solve it (for example some module flag "restart after deactivation")? AFAIK Jirka plans to disable "live" deactivation for 6.0. It looks most likely that there is a bug in the mobility editor kit - it is failing to remove itself during module deactivation? But hard to tell for sure. No deactivation in 6.0+ (unless you use the Module Manager), so I don't plan to fix. No idea how I could fix anyway - some asynchronous code is running using stale data. Would require major overhaul of NB internals to fix this kind of bug reliably. |