Eclipse Community Forums: Java Development Tools (JDT)

Home » Language IDEs » Java Development Tools (JDT) » JDT Search caching

JDT Search caching [message #202129]

Thu, 28 April 2005 11:54

Eclipse User

In M6 there was an internal class called AllTypesCache which would use
the search engine to determine types of a name and used to cache the
results etc. It also used to listen to type changes and kept the cache
update i think.

In M7 this has been removed. I was wondering as to how one can find
similar functionality without making the SearchEngine perform a full search?

Regards,
Sri.

Re: JDT Search caching [message #202147 is a reply to message #202129]

Thu, 28 April 2005 22:33

Eclipse User

Originally posted by: akiezun.remove.mit.edu

Sri Gunturi wrote:
>
> In M6 there was an internal class called AllTypesCache which would use
> the search engine to determine types of a name and used to cache the
> results etc. It also used to listen to type changes and kept the cache
> update i think.
>
> In M7 this has been removed. I was wondering as to how one can find
> similar functionality without making the SearchEngine perform a full
> search?
>
> Regards,
> Sri.

imo, your best best is to do what the open type dialog does
it used to use the all type cache, now it uses the engine, afaik.

/adam

Re: JDT Search caching [message #202913 is a reply to message #202147]

Mon, 09 May 2005 05:16

Eclipse User

We now use the search engine, which has been enhanced to use a fast
workspace index (SearchEngine#searchAllTypeNames(...))

Cheers

Tobias

"Adam Kiezun" <akiezun@remove.mit.edu> wrote in message
news:d4s6kh$uls$1@news.eclipse.org...
> Sri Gunturi wrote:
>>
>> In M6 there was an internal class called AllTypesCache which would use
>> the search engine to determine types of a name and used to cache the
>> results etc. It also used to listen to type changes and kept the cache
>> update i think.
>>
>> In M7 this has been removed. I was wondering as to how one can find
>> similar functionality without making the SearchEngine perform a full
>> search?
>>
>> Regards,
>> Sri.
>
> imo, your best best is to do what the open type dialog does
> it used to use the all type cache, now it uses the engine, afaik.
>
> /adam

Previous Topic:	Memory Leak?
Next Topic:	OutOfMemory error

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Aug 30 06:20:50 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter