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 forums. But to date, it's tough to reconcile information from the two independent camps. :)
I suspected that AJ just uses whatever classloader is provided to it. That's kind of what it looked like to me. But I couldn't/don't understand how the Agent bootstraps though. From what I can tell, its the base JVM's classloader that calls the Agent premain, and instructs it to instrument the classes. In which case, I would expect any visibility of that classloader to extend to AJ as well.
So given that the AJ Weaver doesn't find the classes, I figure that WF is doing something with/to it. But in that case, I dont understand at all how the JVM's instrumentation works; I guess I'm confused where in the cycle the instrumentation is called when loading classes. Do you know if there are any docs or whitepapers I can read up on how the classloader/instrumentation cycle works? I couldn't find enough clarity on the Oracle site.
Thanks,
Eric