Hi Alex,
You're right. There is no real reason other than laziness to try to advise container classes. I'm actually trying to log EJB authorization, so instead of advising every EJB method, I was thinking of advising the container's authorization interceptor and checking if the interceptor throws an exception. I guess the non-lazy (proper ?:)) way is to advise all secured EJB methods. I'll have to give that a shot tomorrow. But it just made me think/wonder if there was any way to advise classes that were already loaded.
It also doesn't address my issue when I am trying to LTW classes that are only visible to the child classloader but not the classloader that loaded the apsects. Which means that I still don't know how to access the advised parameters/return values.
Any thoughts which flags I should use to get the most info out of the advise process? I have the verbose flag enabled in my aop.xml, but it doesn't seem to give me enough details. I know I get more details out when using CTW with ajc, but I suspect that is because it knows exactly which methods it can match on compile, vs LTW when it never knows if it matches or not until the classes are loaded. So you never get warnings that pointcuts don't match.
Thanks!
Eric