Here's the situation, I am editing some Java code (class file) in project that only contains Java classes and no JSP. I right click on an identifier and select "References" and then specify the scope as being the project. The Java search happens quickly. But then a JSP Search dialog comes up and can stay up for a minute or more.

If the project has no JSP files, this should be fast or not occur at all!

In addition, this also happens if you select a directory in Package Explorer (e.g., the java src directory) and use the Search Java dialog. There are no JSP files in the selected resource.

JSP search speed has been an issues in all versions of Eclipse since I started use MyEclipse (v3 or 4 I forget). I keep hoping that they will be fixed in the next version... but they haven't. Any hope that someone is working on this and it will be fixed "in the next version..."

Alternatively is there a way to turn ALL JSP search functionality off. (since most of my code uses Tags now, it's pretty worthless anyway...)

Granted, I have a very complex workspace environment with 70+ projects and 6K worth of JSP files. Plus there are 3-4 layers of dependencies between a large repository of jars (e.g. commons, et. al), a set of core library code projects, and a bunch of individual web projects. But these days, this is becoming common.

Before someone gives me the standard... use -clean or re-import your projects into a new workspace to get rid of old stuff.... I've already done that. Last time was when I migrated to the all-in-one 6.0 version. Took two days to get all the dependencies re-set up, etc. Not something that I want to do again.

Here's my install info:

*** Date:
Thursday, July 30, 2009 10:05:08 AM EDT

** System properties:
OS=WindowsXP
OS version=5.1.0
Java version=1.6.0_13


*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 7.5
Build id: 7.5-20090609


*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 7.5
Build id: 7.5-20090609




Eclipse Plug-in Development Environment

Version: 3.4.2.R342_v20090122-7T7U1E9imVKz-A8Vz-p_jRS
Build id: M20080703-0800


Eclipse Platform

Version: 3.4.2.R342_v20090122-9I96EiWElHi8lheoJKJIvhM3JfVsYbRrgVIWL
Build id: M20090211-1700


Eclipse Graphical Editing Framework GEF

Version: 3.4.2.v20090218-1145-67728084A56B4I233613552
Build id: 200809101400


Eclipse RCP

Version: 3.4.200.R342_v20090122-989JESTEbig-SVaL8UJHcYBr4A63
Build id: M20090211-1700


Eclipse Java Development Tools

Version: 3.4.2.r342_v20081217-7o7tEAoEEDWEm5HTrKn-svO4BbDI
Build id: M20090211-1700




Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Dev\Eclipse\MyEclipse7.0\myeclipse.exe
-name
Myeclipse
--launcher.library
C:\Dev\Eclipse\MyEclipse7.0\../MyEclipseCommon\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731\eclipse_1115.dll
-startup
C:\Dev\Eclipse\MyEclipse7.0\../MyEclipseCommon\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20081125.jar
-exitdata
16d0_40
-clean
-configuration
configuration
-vm
C:\Dev\Eclipse\MyEclipseCommon\binary\com.sun.java.jdk.win32.x86_1.6.0.013\bin\javaw.exe

monroe,

I've sent your request in to the developer responsible for this feature. Unfortunately there is no way that I know of to turn the JSP reference search off entirely.

Instead of using the Reference search from the context menu, if you select the project and bring up the Search > Java dialog with the "Selected Resources" option selected, does it work as expected? I realize this is not a viable replacement for the fast context menu search but would like to know if that works for you; that will help us find the problem sooner.

Do other projects (which contain JSPs) depend the project within which you are searching or is it completely isolated?

There is currently no way to scope the reference search atm. I opened a request in our internal bug tracker.

Re: Using Search > Java

Mentioned that in my initial post but tested again. Both ways have the same symptoms.

Re: Dependencies

Same behavior occurs in "standalone" projects w/o JSP file (e.g. some Apache Projects I've got for reference).

Some additional test results:

Played around with closing various projects (NOTE: have 70+ projects... but tend to have 10-20 open at one time). The time that the JSP Search dialog stays up seems to be related to the number of projects with JSP files open. Haven't found a magic number yet.

Also, another quick fix suggestion would be to make the Cancel button on the JSP Search dialog work quickly. It seems to be blocked while the "JSP Indexes are being searched....". At least it seems that way.