| Summary: | [1.5][dom] null binding for ClassInstanceCreation | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Frederic Fusier <frederic_fusier> |
| Component: | Core | Assignee: | Olivier Thomann <Olivier_Thomann> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | philippe_mulet |
| Version: | 3.1 | ||
| Target Milestone: | 3.1 RC2 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
Same issue of course with #test018 with ClassInstanceCreation on class B and class C.. Investigating. Candidate for RC2. In fact, no changes are required in the DOM converter. The problem resides in the QualifiedAllocationExpression where the resolvedType is not persisted. +1 for RC2 Fixed and released in HEAD. Regression test added by updating ASTConverter15Test.test0017 Verified for 3.1 RC2 using build N20050607-0010 + JDT/Core HEAD Verified for 3.1 RC2 using build I20050610-0010 |
Using 3.1 RC1. Looking at ASTConverter15Test#test015 sample in ASTView, I see a null binding for ClassInstanceCreation in main method: public class X { public static void main(String[] args) { test0017.A<String>.B<Integer> o = new test0017.A<String>("Hello").new B<Integer>(new Integer(1)); System.out.println(o); } } Note that it's second ClassInstanceCreation which is null: new test0017.A<String>("Hello").new B<Integer>(new Integer(1)) first one binding si not null and well set: new test0017.A<String>("Hello")