The following classes are not exposed to the LTW infrastructure regardless of the aop.xml file(s) used:
Despite these restrictions, it is perfectly possible to match call join points for calls to these types providing the calling class is exposed to the weaver. Subtypes of these excluded types that are exposed to the weaver may of course be woven.
Note that dynamic proxy representations are exposed to the LTW infrastructure and are not considered a special case.
Some lint options behave differently when used under load-time weaving. The adviceDidNotMatch won't be handled as a warn (as during compile time) but as an info message.