1 Reply Latest reply on May 28, 2006 4:15 PM by kabirkhan

JBAOP-204 Superclasses get instrumented first with loadtime

stalep May 24, 2006 9:14 AM

Hi, with help/hints from Kabir ive commited a fix for this into cvs.
Ive extracted all of the weaving away from AspectManager to a WeavingStrategy
(ClassicWeavingStrategy and SuperClassesFirstWeavingStrategy).
It will only use SuperClassFirstWeaving at loadtime and if generated advisors is selected.
Kabir talked about caching in the SuperClassFirst strategy, but that isnt implemented yet (some code exists, but not completed).
Added an extender test to check that superclassfirst strategy also works with a large hierarcy of classes.

1. Re: JBAOP-204 Superclasses get instrumented first with loadt

kabirkhan May 28, 2006 4:15 PM (in response to stalep)

Thanks,

That was the final main hurdle to be able to switch to the aop 2 "generated advisors" weaving model. I have now got all the aop tests passing with generated advisors (including the scoped one).

One more thing that needs testing is
http://jira.jboss.com/jira/browse/JBAOP-257, it can be based on the "extender" and "scoped" aop testsuite tests.
Actions