Description bdferris@cs.washington.edu 2010-11-25 04:13:18 EST

Build Identifier: 20100917-0705

When editing a JSPX file that references a taglib in a local Eclipse project, trying to type a new element in the editor would cause Eclipse to hang for 5-10 seconds.  Specifically, I could type the "<" character, but when I typed the first character of the element name, Eclipse would hang.

I had to pull up the org.eclipse.jst.jsp.core plugin in another workspace and walk through the code in the debugger while running my normal workspace in another Eclipse instance to figure out what was going on.  I eventually traced the slowdown to the amount of time being taken by the ProjectDescription.index() method when it was attempting my webapp.

My project is a Maven webapp, with the requisite /target build directory.  The build directory contained an exploded copy of the war built during a project packaging phase.  The indexer was attempting to index each JAR file in the exploded war and that took a significant amount of time.  Thus, Eclipse seemed to hang.

It doesn't seem like WTP should be indexing my project's entire /target directory every time I attempt to type an element name in a JSPX editor.  Seems like a reasonable fix would be to ignore the /target directory in the Indexer, but maybe there is a more appropriate way?

Reproducible: Sometimes

Steps to Reproduce:
Seems to depend on if the ProjectDescription was cached in the TaglibIndex.fProjectDescriptions cache or not.  The cache holds a relatively small number of elements, so the likelihood of my project being cached is pretty low.