[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[aspectj-dev] Named advice
- From: "Matthew Webster" <matthew_webster@xxxxxxxxxx>
- Date: Mon, 18 Aug 2003 16:16:57 +0100
- Delivered-to: firstname.lastname@example.org
- Importance: Normal
I have discovered another reason for named advice: backwards compatibility
for binary aspect libraries.
Currently the advice name e.g. "ajc$before$coverage_Coverage$29c" is based
on the position in the source file where the advice is declared.
Unfortunately if a trivial change is made to the aspect e.g. a comment is
added the name changes. This makes binary aspect libraries that use
abstract aspects as an "interface" extremely fragile: any clients must be
rewoven. Although current guidelines suggest keep advice as thin as
possible small changes to the aspect may be necessary. It would also be
nice to able to add pointcuts and advice, perhaps to the end of an aspect,
and maintain backwards compatibility similar to that offered by Java
classes. Was numbering of advice sequentially in the source, starting
perhaps with $1 like anonymous inner classes, not considered?
I suppose what we really need is the equivalent of the serialVersionUID for
object serialization with a name generated based on the definition of the
pointcuts on which it depends.
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
The IBM Academy is sponsoring a conference on Aspect-Oriented Software
Development, 3rd-4th September, Yorktown, NY.