Summary: | Problem with order of change listeners (1GKXGAT) | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Martin Aeschlimann <martinae> |
Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
Status: | RESOLVED WONTFIX | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | James_Moody |
Version: | 2.0 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | Windows NT | ||
Whiteboard: | |||
Bug Depends on: | |||
Bug Blocks: | 4247 |
Description
Martin Aeschlimann
2001-10-10 22:54:49 EDT
PRODUCT VERSION: 202 *** Bug 6045 has been marked as a duplicate of this bug. *** The current state is that the type hierarchy (TypeHierarchyLifeCycle) contains a workaround where the element change listener is always added after the type hierarchy listener. Having that, the type hierarchy change notification only sets a flag in the TypeHierarchyLifeCycle, but the change is processed in the following element change notification. It's a workaround that makes assumtions that listeners order is not changed, and makes assumtions of how hierarchies are added as change listeners. These assumtions are undefined, so we should address the problem anyway. I suggest that JavaCore has an internal queue of element listeners for type hierarchies. These listeners are notified first, before all client java element listeners. Defer As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you. |