Bug 13325 - Problem in Search/Decorating labelproviders - was: Java Browsing: Package disapears after rename
Summary: Problem in Search/Decorating labelproviders - was: Java Browsing: Package dis...
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows NT
: P1 critical (vote)
Target Milestone: 2.0 M5   Edit
Assignee: Dani Megert CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-04-10 10:50 EDT by Dani Megert CLA
Modified: 2002-04-11 11:59 EDT (History)
0 users

See Also:

Attachments
log (29.02 KB, text/plain)
2002-04-10 10:57 EDT, Dani Megert CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2002-04-10 10:50:48 EDT 
The old package is removed but the new package is not added.
There's an error in the label provider (see attached log).
Comment 1 Dani Megert CLA 2002-04-10 10:57:39 EDT 
Created attachment 566 [details]
log
Comment 2 Dani Megert CLA 2002-04-10 11:08:21 EDT 
Was hard to reproduce: the problem appears if the Search view contains results
which disappear during the refactoring.

It seems that the global event distributor stops distributing if a component
throws an exception. Therefore the renamed package sometimes doesn't appear.

I guess the trick where I handle the case of non-existing working copies is
somehow broken by the new CombinedLabel stuff that workbench introduced. Not
sure though.

This is a must fix.
Comment 3 Dani Megert CLA 2002-04-10 11:11:43 EDT 
Sometime rename in Projects and Packages view removes the element even if no
search markers are there.
Comment 4 Erich Gamma CLA 2002-04-10 18:26:49 EDT 
Dani pls investigate who is causing this problem.
Comment 5 Dani Megert CLA 2002-04-11 11:47:57 EDT 
The errors in the log are cause by renaming a CU.
This is an old unsolved problem:
  Bug 3601: Can't handle rename of resource (1GCE1EI)
Added a (dirty) workaround for the problem: patching the J Core handle identifier.

Leaving open for investigation of project/package rename problem.
Comment 6 Dani Megert CLA 2002-04-11 11:59:16 EDT 
Fixed rename problem in Java Browsing perspective