Bug 87929 - Wrong decoding of type signature with wildcards
Summary: Wrong decoding of type signature with wildcards
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.1 RC1   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-14 10:13 EST by Martin Aeschlimann CLA
Modified: 2005-05-15 05:51 EDT (History)
1 user (show)

See Also:


Attachments
Regression test (3.01 KB, patch)
2005-05-13 10:54 EDT, Jerome Lanneluc CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Aeschlimann CLA 2005-03-14 10:13:30 EST
20050314

Do (programatically) a code resolve on the following variable type:
class A {
  Map<?, ? extends Set<? super ServerSocket>> z;
}

You get back a Java element that has resolved information and a key of:

  Ljava/util/Map<*+Ljava/util/Set<-Ljava/net/ServerSocket;>;>;

Use BindingKey to get a Signature:

  Ljava.util.Map<*L+;Ljava.util.Set<-Ljava.net.ServerSocket;>;>;

Signature.getTypeArgument returns the wrong number and invalid elements:
  *
  L+;
  Ljava.util.Set<-Ljava.net.ServerSocket;>;
Comment 1 Jerome Lanneluc CLA 2005-05-13 10:54:18 EDT
Created attachment 21110 [details]
Regression test

Cannot reproduce with I20050513-0010. Added regression test
ResolveTests_1_5#test0095()
Comment 2 Jerome Lanneluc CLA 2005-05-15 05:51:29 EDT
Regression test released.