Determine whether or not this pointcut matches a method call to the given constructor, made outside
of the scope of any method or constructor, but within the callerType.
Determine whether or not this pointcut matches a get of the given field outside of the
scope of any method or constructor, but within the given type (for example, during
static initialization).
Determine whether or not this pointcut matches a set of the given field outside of the
scope of any method or constructor, but within the given type (for example, during
static initialization).
Determine whether or not this pointcut matches the execution of a given exception
handler outside of the scope of any method or constructor, but within the handling type.
Determine whether or not this pointcut matches a method call to the given method, made outside
of the scope of any method or constructor, but within the callerType (for example, during
static initialization of the type).
When extending AspectJ's pointcut parsing and
matching with custom PointcutDesignatorHandlers,
it may be necessary to match based on context information
at a join point not exposed simply by java.lang.reflect
member information or argument values.
True if the pointcut expression may match some join points at this
shadow (for example, some calls to the given method may match, depending
on the type of the caller).
This method converts such a string into a Java type declaration like 'void main(String[])' and throws a
'ClassFormatException' when the parsed type is invalid.
MINOR -
Static variable in interface org.aspectj.apache.bcel.Constants
MINOR_1_1 -
Static variable in interface org.aspectj.apache.bcel.Constants
MINOR_1_2 -
Static variable in interface org.aspectj.apache.bcel.Constants
MINOR_1_3 -
Static variable in interface org.aspectj.apache.bcel.Constants
MINOR_1_4 -
Static variable in interface org.aspectj.apache.bcel.Constants
MINOR_1_5 -
Static variable in interface org.aspectj.apache.bcel.Constants
MINOR_1_6 -
Static variable in interface org.aspectj.apache.bcel.Constants
Does the munger have to check that its exception are accepted by the shadow ? It is not the case for annotation style around
advice, for example: that can throw Throwable, even if the advised method does not throw any exceptions.