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: | Events are fired while DataObjectPool is in 'atomic' state | ||
---|---|---|---|
Product: | platform | Reporter: | Svata Dedic <sdedic> |
Component: | Data Systems | Assignee: | Jaroslav Havlin <jhavlin> |
Status: | NEW --- | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 7.3 | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | Possible fix |
Description
Svata Dedic
2013-07-01 14:09:43 UTC
Created attachment 142133 [details] Possible fix > More elaborate fix would postpone the DataObject.firePropertyChange(PROP_VALID) > until after the DataObjectPool.runAtomicAction completes. DataObject.setValid(boolean) uses a vetoable change event for property PROP_VALID, so it needs to be fired immediately. > A simple fix would be to offload DataNode fireNodeDestroyed to a request > processor, so that the DataObject.dispose() and call above it complete, unlock > the DataObjectPool. The NodeDestroyed change can fired later in EDT. Please check the attached patch. (I've also tried to fire all events asynchronously, but it made some tests fail.) Thank you. |