By default if you weave aspects on top of aspects then we use a model where
we revert to the original class file before the first set of aspects was
applied and apply all of them (the original aspects plus the new ones) at
the same time to ensure consistency. This behavior is configurable using
I have a multi-module EAR application that is comprised of:
- EJB jar
- WAR
- aspect library
- supporting libs
My AspectJ library is designed to be used as LTW; it has pointcuts
targetting some of the 3rd party libs.
I have now created a new jar module in which I would like to use CTW. I
have
