|Re: [aspectj-users] AspectJ third-party class is not weaved in weblogic|
Correction, see below:
Alexander Kriegisch schrieb am 03.03.2019 10:11:
Without an MCVE it is difficult to say anything definitive, but in general you seem to have one of two possible problems:
- Class visibility issues due to classloader isolation inside your container (application server): Maybe the two classloaders loading the aspect JAR and the WAR/EAR to be woven are isolated from each other.
- Class-loading order: Maybe your aspect JAR is loaded after the target classes have already been
wovenloaded.There might be other possible causes, I am by no means a container expert because I mainly work with Java SE and without application servers. I think you need to change your configuration in order to address this issue. What to do exactly is beyond my knowledge. Maybe Andy knows more. Maybe it would also help to push an MCVE to GitHub for everyone to reproduce to problem.
yev yev schrieb am 02.03.2019 16:19:
java -javaagent:aspectjweaver.jar -cp ...
[ChangeAwareClassLoader@48537e4f] info AspectJ Weaver Version 1.7.1 built on Thursday Sep 6, 2012 at 16:39:22 GMT [ChangeAwareClassLoader@48537e4f] info register classloader weblogic.utils.classloaders.ChangeAwareClassLoader@48537e4f [DependencyClassLoader@4d5932c7] info using configuration <path_to_my_aop.xml>
debug weaving '<third.party.class>'
[GenericClassLoader@62b46385] debug weaving 'com.core.BasicSessionBean'
Back to the top