Bug 28752 - J Search resports non-existent Java element
Summary: J Search resports non-existent Java element
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.1 M5   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-12-20 10:55 EST by Dani Megert CLA
Modified: 2003-02-11 11:58 EST (History)
0 users

See Also:

Attachments
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-12-20 10:55:19 EST 
It seems that for some matches (most likely binary fields)  a non-existent Java
element is returned as enclosingElement in accept(...).

Test case: Import Team UI plug-in  into a fresh workspace, then search for
SyncCompareInput

You'll see ugly icons (or a ? once bug 28369 is fixed) in the Search view.

Here's the debugger value of such an enclosingElement:
listener (not open) [in SyncCompareInput$2 [in SyncCompareInput$2.class [in
org.eclipse.team.internal.ui.sync [in teamui.jar [in org.eclipse.team.ui]]]]]
Comment 1 Jerome Lanneluc CLA 2003-01-14 04:55:38 EST 
When creating a type handle, now ensures it is a top level type.
Comment 2 David Audel CLA 2003-02-11 11:58:03 EST 
Verified.