Description Thomas Bensler 2008-07-15 05:40:14 EDT

Build ID:  I20080617-2000

Steps To Reproduce:
1. create a java project "common" having one interface

package test.common;
public interface I {
    public void doIt();
}

2. create a java project "client" depending on "common" having one class

package test.client;
import test.common.I;
public class Client {
    public Client() {
        ((I)null).doIt();
    }
}

3. create a java project "server" depending on "common" having one class

package test.server;
import test.common.I;
public class Impl implements I {
    public void doIt() {}
}

4. position cursor on doIt() in class Impl, right click for context menu, choose "open call hierarchy"

5. ensure that the call hierarchy view is in "Show Caller hierarchy" mode. 

6. Client.<init()> is not found being a caller (search cope might be "Workspace" or "Hierarchy")

You might raise the objection that this behavior is fine because the classes Impl and Client are not visible to each other as they reside in sibling projects.

counter-argument:
opening the class hierarchy of interface I when being in class Client shows the Impl class. Each known implementation of an interface method should be presumed as possible target of calling that interface method