Bug 271730 - Allow lazyTjp for after returning + after throwing at same jp
Summary: Allow lazyTjp for after returning + after throwing at same jp
Status: NEW
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: 1.6.4   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-09 02:25 EDT by Ron Bodkin CLA
Modified: 2013-06-24 11:06 EDT (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 Ron Bodkin CLA 2009-04-09 02:25:52 EDT
I have two advices (after returning & after throwing) that want to create thisJoinPoint only in certain cases, unfortunately I get told they conflict, so lazy tjp isn't available:

can not implement lazyTjp at joinpoint

    after(Object object) returning: monitorInstance(object) {        
...
    }

    after(Object object) throwing (Throwable t): monitorInstance(object) {
...
    }


It would be nice if these independent forks wouldn't conflict for lazily instantiating tjp
Comment 1 Andrew Clement CLA 2013-06-24 11:06:58 EDT
unsetting the target field which is currently set for something already released