Bug 15561 - Java method search for reference generates invalid result
Summary: Java method search for reference generates invalid result
Status: RESOLVED DUPLICATE of bug 13183
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows NT
: P4 normal (vote)
Target Milestone: ---   Edit
Assignee: Dani Megert CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-08 13:50 EDT by Adalbert Homa CLA
Modified: 2002-05-13 08:25 EDT (History)
0 users

See Also:


Attachments
Example project without the libraries (2.39 KB, application/octet-stream)
2002-05-08 14:04 EDT, Adalbert Homa CLA
no flags Details
Screen captures (388.05 KB, application/octet-stream)
2002-05-08 14:23 EDT, Adalbert Homa CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Adalbert Homa CLA 2002-05-08 13:50:45 EDT
When I am search for a reference of method in Eclipse, I got invalid results and
a an strange message box. 
The search is execute by selecting the method name in the outline, right click, 
References | Workspace. If I restrict the search to Source only (not libraries)
it works fine.

Both M5 and the 20020502 integration build is showing this behaviour.

I will add the example project that has this behaviour and some screen shots.
Comment 1 Adalbert Homa CLA 2002-05-08 14:04:04 EDT
Created attachment 775 [details]
Example project without the libraries
Comment 2 Adalbert Homa CLA 2002-05-08 14:14:36 EDT
The libraries where just to big to be uploaded. Here are the link where they can
be found. 
http://xml.apache.org/dist/xerces-j/old_xerces1/ xerces 1.4.3 (I don't think the
version matters too much).
http://castor.exolab.org/download.html castor 0.9.3. The source code probably
needs to be repackaged to be accepted by Eclipse.

Comment 3 Adalbert Homa CLA 2002-05-08 14:23:57 EDT
Created attachment 778 [details]
Screen captures
Comment 4 Erich Gamma CLA 2002-05-11 07:25:45 EDT
The libraries likely pre-req some other classes internally. When searching the 
code is analyzed but the types cannot be resolved because of incomplete type 
information. Hence the matches are reported as potential, which is shown in the 
result and also indicated in the dialog.

The behaviour is correct what this PR indicates is that the surfacing of 
potential matches isn't as understandable to the user as it should be. 

Dani, time permitting we should do another revisit of this issue.
Comment 5 Dani Megert CLA 2002-05-13 03:41:08 EDT
Attachments unusable since the type is not specified.
gif? jgp? bmp?...
Comment 6 Dani Megert CLA 2002-05-13 04:54:17 EDT
There's already a bug about the Potential Matches dialog (13183).
And also PR against how potential matches are dispalyed in the viewer (15317 ).


*** This bug has been marked as a duplicate of 13183 ***
Comment 7 Adalbert Homa CLA 2002-05-13 08:25:49 EDT
All attachment are zip archives.