I don't see why you can't do this, but you will take a performance hit as it weaves at run time.
It is best if you can apply the aspects during compilation, but if that isn't an option then run time is your other option. On May 18, 2012 6:10 AM, "jbolger" <john.bol...@gmail.com> wrote: > Hi, > > Can you tell me if I can configure an aspect within an EAR to apply advice > against all code (including jars and wars) within the EAR and it's lib > (without having to define the aspect in each of the wars)? > > Also in this case, which weaving style is most appropriate? Is it even > possible to perform compile/post-compile time weaving for an EAR when the > jars / wars it includes have already been built? > > And finally, is any weaving style more performant than the other? > > Thanks in advance, > John > > -- > View this message in context: > http://aspectj.2085585.n4.nabble.com/Aspect-in-an-EAR-file-tp4644307.html > Sent from the AspectJ - users mailing list archive at Nabble.com. > _______________________________________________ > aspectj-users mailing list > aspectj-users@eclipse.org > https://dev.eclipse.org/mailman/listinfo/aspectj-users >
_______________________________________________ aspectj-users mailing list aspectj-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users
