Bugzilla – Full Text Bug Listing
| Summary: | super-qualified pointcut reference cause weaver stack trace | ||
|---|---|---|---|
| Product: | [Tools] AspectJ | Reporter: | Wes Isberg <wes> |
| Component: | Compiler | Assignee: | Jim Hugunin <aspectj> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P2 | CC: | rbodkin+LISTS |
| Version: | 1.1.0 | ||
| Target Milestone: | 1.1.1 | ||
| Hardware: | PC | ||
| OS: | Windows NT | ||
| Whiteboard: | |||
Sorry, workaround of removing "super" is wrong in cases where the pointcut is
being redefined in the current aspect. In this case, the workaround is to
specify the super-type instead:
from: super.pc()
to: AA.pc()
where: AA is the relevant supertype
super is not allowed in pointcut definitions in AspectJ-1.0 or 1.1. It seems like a reasonable thing to ask for in 1.2. However, having a stack trace for any unknown type name in this position is terrible and easily fixed. This is now fixed in the tree for 1.1.1. (Note: This bug will be actually marked fixed (and P2) when I get my eclipse account to work with my new email) FIXED |
"super.{pointcut}(..)" causes the weaver to throw an exception: org.aspectj.weaver.BCException: Bad type signature: <missing> at org.aspectj.weaver.TypeX.signatureToName(TypeX.java:565) at org.aspectj.weaver.TypeX.getName(TypeX.java:205) ... The "super" is unnecessary since the pointcut is implicitly qualified by the enclosing type, so it can be removed to avoid the stack trace. Find test case in modules/tests/bugs/SuperPointcutCE.java