Summary: | IllegalStateException thrown: Expecting raw type | ||
---|---|---|---|
Product: | [Tools] AspectJ | Reporter: | Felix Mayer <felix.mayer> |
Component: | IDE | Assignee: | aspectj inbox <aspectj-inbox> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 1.5.2 | ||
Target Milestone: | 1.5.3 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Felix Mayer
2006-08-04 11:15:12 EDT
Once this problem has occurred, all *.aj files are opened with the Java editor instead of the AspectJ editor. we've fixed a few cases of this ... guess this is another one.... I've reproduced this failure - not sure if its via the route the raiser is using but I'm going to fix the case I've found. I have a Java5 type with a member: Pair<String,String> foo; Where Pair is: class Pair<A,B> {} All fine.... the problem I see is because after initial compilation, in an LTW environment, we reuse the type containing the member 'foo' in an situation where Pair is not-generic (ie. probably a back level of the library containing Pair). The code that unpacks the signature for the member is expecting Pair to be in its 'raw' form (ie. it is actually a generic type underneath) - when we discover it isnt, we go bang. In these situations where we cannot parameterize the non-generic type, we'll continue with the simple type that has been found. I can't immediately think of a situation where this will get us into trouble. I am adding trace entries for this situation so that it is logged in future and we can more easily diagnose what is going wrong. i think this has now been resolved - we allow the type that was discovered to be non-generic and continue with the simple type. please reopen if it still happens for you. |