Bug 395225 - ProceedingJoinPoint.StaticPart
Summary: ProceedingJoinPoint.StaticPart
Status: NEW
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: 1.7.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL: http://aspectj.2085585.n4.nabble.com/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-27 18:35 EST by Hmil P CLA
Modified: 2012-11-29 11:02 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hmil P CLA 2012-11-27 18:35:17 EST
I am requesting for a ProceedingJoinPoint.StaticPart which would allow proceeding in around advice without requiring a call to makeJP.

In my situation, I am implementing a profiler in @AspectJ, to log the time a given method takes and am only interested in thisJoinPointStaticPart.getSignature() and the arguments to the method execution. There are two options to do this, both with drawbacks:
1. Using before and after advice, maintaining a stack per thread of the function calls
--the stack is prohibiting for performance
2. Using around advice
--a join point is constructed on every method execution

Please see this thread for the entire discussion: http://aspectj.2085585.n4.nabble.com/lazyTJP-optimization-for-around-advice-td4650646.html
Comment 1 Andrew Clement CLA 2012-11-29 11:02:29 EST
just a note whilst I remember. The need for a proceedingjoinpoint to have something to proceed upon may make this non trivial to implement in an optimal way (it won't be as trivial as the regular JoinPoint.StaticPart).