Re: [aspectj-users] How to ensure AspectJ aspects are LTW'ed by Wildfly's modules?

> I suspected that AJ just uses whatever classloader is provided to it. Yes, exactly. Because we don’t want to get into tricks around classloaders. I am a bit rusty but I think for weaving a particular type you can see the entry point in the type Aj is driven every time something is loaded once

Re: [aspectj-users] How to ensure AspectJ aspects are LTW'ed by Wildfly's modules?

I did try with my aspect.jar on the bootclasspath with -Xbootclasspath/a (I would be surprised if /a or a /p would make a difference). Didn't make any difference. I haven't tried posting on StackOverflow yet figuring that I would likely get a more targeted response from here or the wildfly-dev f

Re: [aspectj-users] How to ensure AspectJ aspects are LTW'ed by Wildfly's modules?

Did you try your aspect jar on the bootclasspath ? (Just wondering if that might help). AspectJ deliberately avoids getting involved in class loader shenanigans because it gets too complicated, hence relying on the delegation model in place for the system it is being used with. However you mak

Re: [aspectj-users] How to ensure AspectJ aspects are LTW'ed by Wildfly's modules?

Thanks for the info. I've been digging through AJ and WF code some more to try to figure this out, but am still not sure how the classloader is working. I'm starting Wildfly using the following arguments: -Djboss.modules.system.pkgs=org.jboss.byteman,org.aspectj,te st.aspectj,org.jboss.logmanage

Re: [aspectj-users] How to ensure AspectJ aspects are LTW'ed by Wildfly's modules?

Yes, it is a bit specific to wildfly but I can talk to what AspectJ does. I will also call out to an old article I wrote on debugging LTW: http://andrewclement.blogspot.ca/2009/02/load-time-weaving-basics.html (might be u