Bug 9785 - Problem in IType.resolveType()
Summary: Problem in IType.resolveType()
Status: RESOLVED DUPLICATE of bug 7485
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P1 blocker (vote)
Target Milestone: 2.0 M3   Edit
Assignee: David Audel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-02-13 16:26 EST by Scott Rich CLA
Modified: 2002-02-14 09:12 EST (History)
0 users

See Also:


Attachments
modified SelectionEngine.java from 0125 stable build (19.68 KB, text/plain)
2002-02-13 16:28 EST, Scott Rich CLA
no flags Details
modified SelectionEngine.java from 0125 stable build (19.68 KB, text/plain)
2002-02-13 16:28 EST, Scott Rich CLA
no flags Details
SelectionEngine with the fix (21.66 KB, text/plain)
2002-02-14 05:37 EST, David Audel CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Rich CLA 2002-02-13 16:26:42 EST
We use IType.resolveType(unqualifiedName) to get the fully qualified names of 
member types within source types.  It is not working for us in the Eclipse V2 
0125 stable build.

The problem seems to be in org.eclipse.jdt.internal.codeassist.SelectionEngine, 
where selectType(sourceType, name) is eventually called.  It seems that the 
line at the top of this method which sets the private field qualifiedSelection 
equal to the incoming unqualified type name causes the search to fail later on 
in selectFrom(binding).  

Commenting out the set seems to fix the problem.  If I can figure out how, I'll 
attach the modified source.

This is currently blocking several of our components getting up and running on 
Eclipse V2.
Comment 1 Scott Rich CLA 2002-02-13 16:28:14 EST
Created attachment 363 [details]
modified SelectionEngine.java from 0125 stable build
Comment 2 Scott Rich CLA 2002-02-13 16:28:37 EST
Created attachment 364 [details]
modified SelectionEngine.java from 0125 stable build
Comment 3 Philipe Mulet CLA 2002-02-13 17:35:40 EST
David - please investigate asap.

We might want to sneak this one into stable 20020212 (no promise).
Comment 4 David Audel CLA 2002-02-14 05:37:36 EST
Created attachment 365 [details]
SelectionEngine with the fix
Comment 5 David Audel CLA 2002-02-14 05:38:08 EST
Indeed the problem is the field qualifiedSelection.
qualifiedSelection must be set equal to the incoming type name only when type 
name is qualified.

*** This bug has been marked as a duplicate of 7485 ***