Adoption of AOSD is hindered by the fact that it breaks traditional notions of class ownership. An oftrepeated objection is that the developer responsible for a class (the class owner1) no longer has control over the details of the class, because weaving could result in separately-written aspect code affecting class semantics. Modern environment support, such as provided by AJDT [2], helps by showing the sites of weaving impact, and making it easy to navigate to the relevant aspect code, but this still does not give the class owner control.
By: Harold Ossher
Published in: RC24057 in 2006
LIMITED DISTRIBUTION NOTICE:
This Research Report is available. This report has been submitted for publication outside of IBM and will probably be copyrighted if accepted for publication. It has been issued as a Research Report for early dissemination of its contents. In view of the transfer of copyright to the outside publisher, its distribution outside of IBM prior to publication should be limited to peer communications and specific requests. After outside publication, requests should be filled only by reprints or legally obtained copies of the article (e.g., payment of royalties). I have read and understand this notice and am a member of the scientific community outside or inside of IBM seeking a single copy only.
Questions about this service can be mailed to reports@us.ibm.com .