Summary: | NullPointerException for wildcard annotation type pattern match | ||
---|---|---|---|
Product: | [Tools] AspectJ | Reporter: | Mohan Radhakrishnan <javatech> |
Component: | Compiler | Assignee: | Adrian Colyer <adrian.colyer> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | unspecified | ||
Target Milestone: | 1.5.0RC1 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Mohan Radhakrishnan
2005-08-29 03:26:12 EDT
Clarification. The first bean and the aspect with the pointcut shown are both in the same package. The second bean and the annotation are in a different package. Passing over to the compiler There's definitely a bug lurking here, but I couldn't reproduce it yet from the information provided so far. The pointcut you've given in the snippet should compile to a pointcut with an *ExactAnnotationTypePattern* (which it does for me), but in your stack trace you have a *WildAnnotationTypePattern*. I tried a variant in which the propertyChanger annotation was not visible to the aspect, but this just gave the expected type not found message. Could you please attach the full source of your aspect if possible? Also, do you have any other pointcuts or advice in your application that are working with annotations? Is it possible one of these is the culprit? If you could attach a self-contained zip with all files needed to reproduce that would be absolutely fantastic, otherwise we can continue the detective work as is.... Thanks, Adrian. I tried to repeat this but somehow my original configuration is lost. Actually when I moved everything to the same package I didn't see this bug. cant reproduce on our side - but given all the compiler changes, it might have been resolved. Please reopen if it happens again. |