[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [aspectj-users] Met [org.aspectj.lang.NoAspectBoundException] while running a post-compile woven (bytecode woven) apache thrift library
|
@Andy
Thanks for working on this. I agree that in those cases 'privileged' should be necessary. BTW, the original reporter did use 'privileged', thus the idea of improving the unexpected behaviour we found there. :-)
Cheers
--
Alexander Kriegisch
https://scrum-master.de
Andy Clement schrieb am 26.05.2018 02:31:
@Alexander
I wondered if you had an opinion on this. I’ve been working on this under
https://bugs.eclipse.org/bugs/show_bug.cgi?id=535086 . I can’t decide if you should have to specify privileged in order for pertypewithin to match against types not visible from the aspect. Currently I have it so that pertypewithin will no longer match private types or default vis types in another package unless you specify privileged. If you do specify privilege the visibility is raised for those types during weaving so they are accessible (the auto raising of visibility is not unusual, we do it for other reasons at times).
cheers,
Andy
I think there is a visibility issue here - the creation of the aspect fails because in trying to create it we use reflection to invoke a method in the affected type (the type pertypewithin is hitting) and that reflection is failing (silently) because the type isn't accessible. The type visibility should probably have been raised if the type is hit by pertypewithin.
cheers,
Andy