Thanks Ludger J this worked, looks like AspectJ is the way forward.
From: [email protected] [mailto:[email protected]] On Behalf Of Ludger Solbach Sent: 30 October 2013 17:15 To: [email protected] Subject: Re: [aspectj-users] AspectJ and EL Hi, if you use an execution instead of a call pointcut, the code is weaved into the method itself and not around the calls. Then it should be irrelevant, if the method is called from java code, reflectively or via EL. Bye, Ludger Gesendet: Mittwoch, 30. Oktober 2013 um 17:11 Uhr Von: "Wendel Schultz" <[email protected]> An: [email protected] Betreff: Re: [aspectj-users] AspectJ and EL Are you weaving at compile time or using LTW? I'm new here too, but it may on account of classloaders. Sometimes, JSPs are rendered in different classloaders. Each classloader needs their own copy of the woven class (as I understand it). So, if you're using LTW, you'll need to ensure that all your classloaders are weaving properly. Is it remotely possible that this could help? -w On Wed, Oct 30, 2013 at 9:01 AM, Anthony <[email protected]> wrote: Hi, I’ve just installed AspectJ and got it working as expected but I’ve come across an unexpected problem. Everything works fine except when the code is called from EL (through JSF), then it just skips the around advice that I’ve created for it. I can kind of understand why this might be happening as it seems the advice is attached the calling code as opposed the method code (inferring from AJDT behaviour), but is there any way around it? Many thanks, Anthony. _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
_______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
