Bugzilla – Full Text Bug Listing
| Summary: | MethodBinding.java:488 NPE in 1.2rc2 | ||
|---|---|---|---|
| Product: | [Tools] AspectJ | Reporter: | attila lendvai <101> |
| Component: | Compiler | Assignee: | Adrian Colyer <adrian.colyer> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 1.2 | ||
| Target Milestone: | 1.2.1 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
attila lendvai
scenario: - i have a chain of aspects with Intertype Method Declarations. - one of them defines an inner interface with a method (no implementation) - a later aspect in the inheritance defines an implementation for the above method but the return type of the method is not included I'm trying to build a pair of files that simulate this scenario, but I can't
get it to fail. Here's my attempt:
abstract aspect A {
interface Andy {
public String getString(String s);
public void getString(int i);
}
}
And my subaspect:
aspect B extends A {
public String A.Andy.getString(String s) {
return "";
}
}
That compiles fine. I'm not sure what you mean by "but the return type of the
method is not included". If I remove the 'String' return type declaration from
aspect B above then it doesn't compile and gives me a valid error message. Can
you cast an eye over my two aspects above and tell me if theres anything you
are obviously doing differently?
We have just moved AspectJ to the Eclipse 3.0 final version of the JDT compiler rather than the Eclipse 3.0 M6 version. Please can you try a more recent version of version of AspectJ to see if it fixes your problem? Also, all the stack entries have 'moved' with the compiler upgrade - so if you could attach a more recent version of the stack trace, that would be great. This more recent version also includes several fixes for ITD handling that may fix it too. You can get the most recent fully tested version of AspectJ from: http://download.eclipse.org/technology/ajdt/dev/aspectj-DEVELOPMENT.jar I'm closing this bug. We are unable to recreate it and I believe you have moved on from this problem (not to mention that we have replaced the compiler since it was raised) - if you do find it still exists, please reopen this bug. We have recently fixed a problem with array types that could have led to them appearing to be '<missing>' in certain situations which could be related. (And we have fixed several problems relating to complex intertype declaration interactions). And we now have dump support so that when things go wrong like described in this bug report we should produce an 'ajcore.***' file in the directory in which the compiler was executing. This ajcore file captures all the state from the compiler at the time of the crash - please include it in the bug report if you get a future failure. sorry we didnt have the 'cycles' to fully investigate it when you first raised it. thanks, Andy. Fix released as part of AspectJ 1.2.1 |