Use AOP to maintain legacy Java applications
Techniques for dealing with complex and unfamiliar Java code
From the developerWorks archives
Date archived: December 19, 2016 | First published: March 09, 2004
If you've ever inherited and then had to maintain a Java-based legacy application, then this article is for you. Author Abhijit Belapurkar shows you how to use aspect-oriented programming (AOP) to gain an unprecedented view into the inner workings of even the most opaque of legacy applications.
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 steps and illustrations may have changed.