Bug 420345

Description Hubert Lei 2013-10-24 21:28:35 EDT

Created attachment 236867 [details]
use case

This issue is similar to Bug 249567, but not exactly the same.

There are two classes defined within different packages in the same project, but they have the same simple name,e.g. "FrontTyre". A third class can use these two classes as the parameter types of two methods declarations respectively, while those two methods declarations have the same simple name too:

package com.hubert.brandshow;

import com.hubert.merida.FrontTyre;

public class Bike {
	public void showTyre(com.hubert.giant.FrontTyre ft){
		System.out.println(ft.getBrand());
	}
	
//a simple name is used instead of complete name as the parameter type
	public void showTyre(FrontTyre ft){
		System.out.println(ft.getBrand());
	}
}

When parsing the second method declaration, there is an error.

Our parse procedure is following:
1. Acquire methodBinding via IMethodBinding.resolveBinding() method
2. Invoke getJavaElement() method on the method binding to get IMethod.

The first step results in a method binding 
"public void showTyre(com.hubert.merida.FrontTyre)", 
while the second returns the INCORRECT IMethod 
"void showTyre(com.hubert.giant.FrontTyre".

Through debugging, I found in Util.getUnresolvedJavaElement(...), line 1434 can return a correct IMethod, but in line 1437, the result is recognized as not existent. Thus, a wrong result is returned. This might be related to 
" org.eclipse.jdt.internal.core.JavaModelManager.getInfo(IJavaElement element)
"
Complete use case is attached.