News: AOP@Work: AOP and metadata: A perfect match, Part 2 published

  1. IBM developerWorks has published the second and concluding part of Ramnivas Laddad's article series "AOP and metadata: A perfect match". This article is a part of the peer-reviewed AOP@Work series. In this article, Ramnivas describes creating multidimensional interfaces with metadata, explains best practices in using metadata with AOP, and discusses effect of metadata on AOP adoption.
    In the first half of this article, I introduced the basics of the new Java™ metadata facility and explained how and where AOP's join point model could be most beneficially fortified by metadata annotation. I also gave an overview of existing metadata support in three leading AOP systems: AspectWerkz, AspectJ, and JBoss AOP. I touched on the impact of metadata on an AOP system's modularity, and concluded with a refactoring example demonstrating the gradual introduction of metadata annotation into an AOP system.

    In this second half of the article, I'll suggest a novel way to look at metadata as a pathway into multidimensional signature space. This approach has a practical application in untangling element signatures and is also conceptually useful for designing annotation types, even for developers who do not practice AOP. I will also focus on the most beneficial use of metadata annotation in aspect-oriented programming. Among other things, I will demonstrate an effective use of AOP to reduce the loss of modularity that is sometimes associated with metadata annotation. I'll conclude the article with a set of guidelines for determining when and how best to use metadata. I'll also consider the effects of adding a metadata facility on the adoption of AOP.

    As series lead, I welcome commentary from the community regarding individual articles and the series as a whole.

    Threaded Messages (3)

  2. The phase buffer...[ Go to top ]

    "I'll suggest a novel way to look at metadata as a pathway into multidimensional signature space."

    This is programming, only programming. No delithium crystals involved....

    Won't be reading it, but I'll watch the episode.

  3. Insightful article.[ Go to top ]

    Nice job, once again, Ramnivas.

  4. Ramnivas' article provides a great description of the value and need for appropriate meta data descriptions in AOP frameworks models. I just wanted to point out that just as recommended in the article Aspectwerkz has been using Java 5 annotations to mark up AOP code for over a year now. With the convergence of Aspectwerkz and AspectJM in AspectJ 5 we should see these benefits available to a great number of people in the community.

    Adam FitzGerald
    Principal Technologist
    BEA Systems