[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [aspectj-dev] Re: [Bug 55107] add removeLibraryAspect method to weaver



>I am not sure for that types we could use the Class object directly. If
>I remember it correctly the ConcreteName provides also aspect specific
>information that cannot be extracted from a Class object. Do we need
>this information in the LTW case? But we could use it at least for
>classes that are not part of LTW, like the original java.. and javax..
>classes. (In those cases we would also not have any problem with
>re-entrancy.)
>
>What do you think?

The weaver would certainly need access to the byte-code (or at least the
class attributes) for aspects and classes containing pointcuts. For
ordinary classes methods in ConcreteName like "getDeclaredPointcuts()"
would simply return an empty array.

Matthew Webster
AOSD Project
Java Technology Centre, MP146
IBM Hursley Park, Winchester,  SO21 2JN, England
Telephone: +44 196 2816139 (external) 246139 (internal)
Email: Matthew Webster/UK/IBM @ IBMGB, matthew_webster@xxxxxxxxxx
http://w3.hursley.ibm.com/~websterm/