Your error "Cannot find parent aspect for: <concrete-aspect name='org.jboss.as.quickstart.aspects.MyFieldAspect' extends='org.jboss.as.quickstart.aspects.FieldAspect' perclause='null'/> in aop.xml"
does suggest it is a matter of where to put the aspect so that the right class loader will see it. If the application server is not using a ‘normal’ delegation strategy it may not matter if you put it on the bootstrap path as that may not be getting searched by the class loaders involved. AspectJ does nothing special to locate these things (deliberately), it just asks the class loaders involved to locate these things through whatever their normal route is.
I don’t understand what you are describing here? If your aspect has been compiled there will be a .class file for it and within that (visible via javap) you will see runtime visible annotation attributes that capture the @Aspect/@Pointcut/etc annotations. That is what I would recommend, package the aspect code inside the app that will be consuming it. If that works and it doesn’t work when solely provided on the bootstrap class path then it is because the application class loader isn’t doing normal delegation.
cheers, Andy
Hi AspectJ Developer Team,
As per question on why aspectjWeaver does not recognize the apect codded using @Aspect annotation, is there any other configuration so that aspectJweaver identify configured aspects in aop.xml as Aspects.
I add jar containing aspects into bootstrap path.
Regards, Hitesh
_______________________________________________ aspectj-dev mailing list aspectj-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/aspectj-dev
|