This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Navigation should allow going to implementation of interface rather then interface | ||
---|---|---|---|
Product: | java | Reporter: | dmocek <dmocek> |
Component: | Navigation | Assignee: | Jan Jancura <jjancura> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 3.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
dmocek
2007-05-18 19:52:38 UTC
> NB can figure out that myDog is an implementation of Doberman ...
In general this is quite tricky to do. It may look simple in your example, but
how about code like this one:
Dog myDog = Lookup.getDefault().lookup(Dog.class);
There is no way how the IDE could guess what the lookup call would return. The
only thing you can do is to find all implementations of the Dog interface
visible in the scope of this statement and give a user chance to choose one.
There are several "go to implementation" issues. I'm trying to clean them up. Listing all implementations when you Ctrl+click a method name is covered by bug 142112. For reference purposes, if the Debugger is running and myDog is in the current scope, NetBeans *would* know that it was an implementation of Doberman and could navigate to the correct implementation when you Ctrl+click. *** This bug has been marked as a duplicate of bug 142112 *** |