Bug 93451 - pertypewithin causes a NPE during compilation
Summary: pertypewithin causes a NPE during compilation
Status: REOPENED
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: 1.5.0M2   Edit
Hardware: PC Linux
: P5 normal (vote)
Target Milestone: 1.5.0   Edit
Assignee: Adrian Colyer CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-02 16:20 EDT by Oliver CLA
Modified: 2009-08-30 02:49 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 Oliver CLA 2005-05-02 16:20:06 EDT
I just try the pertypewithin to instantiate an aspect per class. This works:

public aspect TestAspekt<T> pertypewithin(verwaltung.test.*) {
    ...
    after() : execution(* *.*()) {
        log.debug(thisJoinPoint);
    }
}

But when I try to use the generic <T> inside the after advice as described in
the AspectJ developer's notebook it does not work.

public aspect TestAspekt<T> pertypewithin(verwaltung.test.*) {
    ...
    after(T t) : execution(* *.*()) && this(t) {
    ...
}

Each time I try to save this I get an alert box with "NullPointerException
thrown: null" (also repeated as reason).
Comment 1 Andrew Clement CLA 2005-05-03 05:38:09 EDT
Basic generics will be working in M3, we'll have a look at this (parameterized
aspects with PTW) for 1.5.0 final.
Comment 2 Adrian Colyer CLA 2005-08-25 05:36:25 EDT
We've decided to remove this feature from the language for the 1.5.0 timeframe
(a concrete generic pertypewithin aspect). Generic abstract aspects *will* be
supported in M4.
Comment 3 Eclipse Webmaster CLA 2009-08-30 02:49:28 EDT
LATER/REMIND bugs are being automatically reopened as P5 because the LATER and REMIND resolutions are deprecated.