Bug 5317 - Reparenting class should refresh hierarchy
Summary: Reparenting class should refresh hierarchy
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: Other other
: P2 major (vote)
Target Milestone: 2.0 M2   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-28 12:24 EST by Carolyn MacLeod CLA
Modified: 2002-01-14 11:59 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Carolyn MacLeod CLA 2001-10-28 12:24:04 EST
Open a hierarchy view that has several layers.
Change the superclass of one of the hierarchy members.
The hierarchy is not refreshed.
Comment 1 Erich Gamma CLA 2001-10-29 06:00:15 EST
Please localize whether this is a viewer refresh or type hierarchy delta 
problem.
Comment 2 Martin Aeschlimann CLA 2001-11-01 04:18:12 EST
11025
can reproduce:
1. Create class A extends Vector
2. Create class B
3. Open type hierachy on A
4. Edit class B to extend A. Save.
5. No changes in the hierarchy view.

The type hierarchy changed is received. An hierarchy.refresh is invoked (in an 
async runnable, so not anymore in the change listener), the tree is refreshed, 
but children of A are empty.

move to jcore.
Comment 3 Jerome Lanneluc CLA 2001-12-12 11:57:34 EST
Problem was in the CommitWorkingCopyOperation that was not forcing the original 
compilation unit to be opened. Thus the delta was wrong and the hierarchy was 
not sending a 'hierarchy need refresh' event.