Bug 130241 - Java Search: An internal error occurred during: "Java Search".
Summary: Java Search: An internal error occurred during: "Java Search".
Status: CLOSED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2006-03-02 18:12 EST by Feng Xiang CLA
Modified: 2009-08-30 02:05 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Feng Xiang CLA 2006-03-02 18:12:22 EST
When search for a Type that does not exist will produce this error:
!ENTRY org.eclipse.core.runtime 4 2 2006-03-02 18:07:54.656
!MESSAGE An internal error occurred during: "Java Search".
!STACK 0
java.lang.NullPointerException
	at org.eclipse.jdt.internal.core.util.Util.indexOfJavaLikeExtension(Util.java:1158)
	at org.eclipse.jdt.internal.core.search.matching.PossibleMatch.getQualifiedName(PossibleMatch.java:110)
	at org.eclipse.jdt.internal.core.search.matching.PossibleMatch.<init>(PossibleMatch.java:41)
	at org.eclipse.jdt.internal.core.search.matching.MatchLocator.locateMatches(MatchLocator.java:1110)
	at org.eclipse.jdt.internal.core.search.JavaSearchParticipant.locateMatches(JavaSearchParticipant.java:94)
	at org.eclipse.jdt.internal.core.search.BasicSearchEngine.findMatches(BasicSearchEngine.java:208)
	at org.eclipse.jdt.internal.core.search.BasicSearchEngine.search(BasicSearchEngine.java:424)
	at org.eclipse.jdt.core.search.SearchEngine.search(SearchEngine.java:532)
	at org.eclipse.jdt.internal.ui.search.JavaSearchQuery.run(JavaSearchQuery.java:135)
	at org.eclipse.search2.internal.ui.InternalSearchUI$InternalSearchJob.run(InternalSearchUI.java:94)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
Comment 1 Frederic Fusier CLA 2006-03-03 05:35:57 EST
I have not enough information to reproduce or understand your problem, so can you answer following questions:
  1) Could you provide a more precise test case?
     Ideally a small project with minimum of classes to reproduce the problem.
  2) What do you really mean by "a Type that does not exist"? Does it mean: not
     on the classpath or do you use Java Search dialog for searching?
  3) Were you searching for references or declarations, workspace or project?
  4) Did you specified some other java like extensions in your plugin?
  5) Can you reproduce it in another project/workspace?

TIA
Comment 2 Frederic Fusier CLA 2006-03-16 05:19:56 EST
Please reopen while providing requested info, thanks
Comment 3 Frederic Fusier CLA 2007-06-21 09:24:35 EDT
Close due to lack of information to resolve this issue...
Comment 4 Denis Roy CLA 2009-08-30 02:05:00 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.