with the fix for JBAOP-433 flavia had some ideas for optimizing the pointcut matching; suggestion for optimization is to classify pointcuts. - "execution(blahblahblah)" would be classified as Execution - "field(...)", classified as field read and field write - "call(...) OR execution(..)", classified as call and as execution this classification would allow the Advisor to get only the relevant pointcut expressions during an interceptor chain build process. a few questions: - how fine grained we should classify the pointcuts? - could this change improve performance in other areas of aop other than rebuilding the stacks? - should we create a special pointcutcollection class (as flavia suggested) that contain the pointcuts and with utilities to fetch them as needed? (basically we should avoid to clutter up AM anymore than it already is) - is there any gain with refactoring out everything thats involving pointcuts from AM? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150302#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...