AOP@Work, Design with pointcuts to avoid pattern density

Usability and maintainability in the JUnit Cook's Tour

From the developerWorks archives

Wes Isberg

Date archived: May 14, 2019 | First published: June 14, 2005

In "JUnit: A Cook's Tour," authors Erich Gamma and Kent Beck discuss the design of JUnit. They point out that TestCase, like key abstractions in many mature frameworks, has a high pattern density, making it easy to use but hard to change. In this installment of the AOP@Work series, Wes Isberg revisits the Cook's Tour and shows you how using AOP pointcuts rather than object-oriented designs can help you avoid some of the pattern density that makes mature designs hard to change.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some content, steps, or illustrations may have changed.

Zone=Java development
ArticleTitle=AOP@Work: Design with pointcuts to avoid pattern density