public interface ProceedingJoinPoint extends JoinPoint
JoinPoint.EnclosingStaticPart, JoinPoint.StaticPart
ADVICE_EXECUTION, CONSTRUCTOR_CALL, CONSTRUCTOR_EXECUTION, EXCEPTION_HANDLER, FIELD_GET, FIELD_SET, INITIALIZATION, METHOD_CALL, METHOD_EXECUTION, PREINITIALIZATION, STATICINITIALIZATION, SYNCHRONIZATION_LOCK, SYNCHRONIZATION_UNLOCK
Modifier and Type | Method and Description |
---|---|
java.lang.Object |
proceed()
Proceed with the next advice or target method invocation
|
java.lang.Object |
proceed(java.lang.Object[] args)
Proceed with the next advice or target method invocation
|
void |
set$AroundClosure(org.aspectj.runtime.internal.AroundClosure arc)
The joinpoint needs to know about its closure so that proceed can delegate to closure.run()
This internal method should not be called directly, and won't be visible to the end-user when
packed in a jar (synthetic method)
|
getArgs, getKind, getSignature, getSourceLocation, getStaticPart, getTarget, getThis, toLongString, toShortString, toString
void set$AroundClosure(org.aspectj.runtime.internal.AroundClosure arc)
arc
- java.lang.Object proceed() throws java.lang.Throwable
java.lang.Throwable
java.lang.Object proceed(java.lang.Object[] args) throws java.lang.Throwable
Unlike code style, proceed(..) in annotation style places different requirements on the parameters passed to it. The proceed(..) call takes, in this order:
Since proceed(..) in this case takes an Object array, AspectJ cannot do as much compile time checking as it can for code style. If the rules above aren't obeyed then it will unfortunately manifest as a runtime error.
args
- java.lang.Throwable