Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 326279 - Java Search should always use the fastest search technique available
Summary: Java Search should always use the fastest search technique available
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Manoj N Palat CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-27 04:43 EDT by Deepak Azad CLA
Modified: 2020-01-10 15:14 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Deepak Azad CLA 2010-09-27 04:43:48 EDT
FUP of bug 325244 comment 6

The SearchEngine.search(...) APIs should *always* use the
fastest way of searching, so that all clients get the fastest
performance possible.

For example - if the search is for *declarations* of method Worker.run(), it is much much faster to 
- use SearchEngine.searchAllTypeNames(..) to find all the 'Worker' classes
- create a Java search scope - SearchEngine.createJavaSearchScope(..) - with these types
- then do a method search - SearchEngine.search() - in this scope

SearchEngine.searchAllTypeNames(..) should also be used for type, field and constructor declaration search.
Comment 1 Eclipse Genie CLA 2020-01-10 15:14:23 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.