Community
Participate
Working Groups
I noticed a strange behaviour in eclipse when I try to use the search references feature (using Ctrl+Shift+G) It works normally on most types, but if I try to do it in a private method my java file to find where it is being used, it does not result anything (even though that method is being used in the class) When I looked at the .log file, I found the following entry - =============== java.lang.NullPointerException: charsetName at java.io.InputStreamReader.<init>(Unknown Source) at com.ibm.sse.model.builder.participants.TaskTagSeeker.setDocumentContent(Unknown Source) at com.ibm.sse.model.builder.participants.TaskTagSeeker.findTasks(Unknown Source) at com.ibm.sse.model.builder.participants.TaskTagSeeker.build(Unknown Source) at com.ibm.sse.model.internal.builder.StructuredDocumentBuilder.build(Unknown Source) at com.ibm.sse.model.internal.builder.StructuredDocumentBuilder$1.visit(Unknown Source) at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:108) at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:55) at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:78) at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82) at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82) at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:123) at org.eclipse.core.internal.resources.Resource.accept(Resource.java:65) at org.eclipse.core.internal.resources.Resource.accept(Resource.java:106) at org.eclipse.core.internal.resources.Resource.accept(Resource.java:85) at com.ibm.sse.model.internal.builder.StructuredDocumentBuilder.doFullBuild(Unknown Source) at com.ibm.sse.model.internal.builder.StructuredDocumentBuilder.build(Unknown Source) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:564) at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:615) at org.eclipse.core.runtime.Platform.run(Platform.java:747) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:157) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:249) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:202) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:229) at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:615) at org.eclipse.core.runtime.Platform.run(Platform.java:747) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:232) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:268) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:297) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:155) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:212) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
That stack trace is from a builder that is not part of eclipse. Can you please provide the class with the private method?
I use Enterprise Workbench 3.8.1 (from www.myeclipseide.org) Sorry, I should probably file a bug under their software. I just didn't know where this error actually came from...... Jalpesh.
The stack trace is not related to the search problem you mentioned. We would still like to track that down if you have a testcase.
Created attachment 14204 [details] sample code select method getExpressionType with the mouse and then press Ctrl+Shift+G instead of finding one reference in the constructor, it returns with zero references.
That works fine for me. I get the one reference in the constructor.
Works fine for me, I tested on RHEL 3 using BEA and IBM JVMs and got the one reference every time.
I've also verified that your example works both 3.0.1 and 3.1. Ok to close?
strange, it still does not work with my install - maybe it has something to do with the fact that I have myeclipseidee installed along with eclipse... Well, if it's not reproducible by anybody, please feel free to close it.... Thanks, and sorry for the trouble..... Jalpesh.
No problem. So, I close it as not reproducable. Reopen if you get it again with a simple test case.
