Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 120534 - Open Type does not work for fully qualified nested type
Summary: Open Type does not work for fully qualified nested type
Status: RESOLVED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 122519
Blocks:
  Show dependency tree
 
Reported: 2005-12-13 05:43 EST by Markus Keller CLA
Modified: 2009-08-30 02:39 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2005-12-13 05:43:08 EST
I20051213-0010

Open Type does not work for fully qualified nested types, e.g java.util.Arrays.ArrayList:

- enter "java.util."
=> "ArrayList - java.util.Arrays" appears

- append "A"
=> "Arrays - java.util" is shown, but Arrays.ArrayList is not available any more

- press backspace to make pattern "java.util." again
=> "ArrayList - java.util.Arrays" is not shown again; removing and re-adding the dot makes the nested class appear again. The nested class should be consistently shown or not shown.

- set pattern to "java.util.Arrays."
=> no type shown; expected: nested types of fully qualified type should be listed
Comment 1 Dirk Baeumer CLA 2006-01-03 10:13:01 EST
The problem is that java.util. list ALL types inside the package java.util whereas java.util.A list all top level types starting with A. This is IMO OK since showing second level types might be confusing. The pattern should then be java.util.*.A.
Comment 2 Dirk Baeumer CLA 2006-01-03 10:38:43 EST
The problem is that from the pattern I don't know if the last segment is a type or a package. I can do some guessing, however this will not work for types with lower case names then. I have change the code that the first segement is always interpreted as a package and the last one as the type you are searching for. This means:

java.util.A: list all types starting with A inside the package java.util even if 
  they aren't top level types.

java.util.Arrays.: will not list any types. The problem is that the search 
  engine doesn't support this. I can hack the code so that it works on a cached
  result but this would introduce another inconsistency.

I have opened bug 122519 to track this issue inside of JDT/Core.

Postponing until 122519 is fixed.
Comment 3 Eclipse Webmaster CLA 2009-08-30 02:39:27 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.