Re:Aspect-oriented? (Score 1)

In our current java project we are using AOP to a certain degree, and I love it.. AOP comes in two flavours: - Introductions - add interface and implementation to your existing classes (kind of support multiple inheritance, as java doesn't) - Advice - add functionality before, after, around your exisiting code. Your existing code in this example may be a method call, a static block executing, a read or write of a class variable. In our projects we are only using advices on methods. We have developed a system that is quite stateless and integrates to a backend system that requires login. So we developed a loginAdvice. Some of the data we retrieve from this system is rather static, so we implemented a cacheAdvice.. We want to track how our customers use our system, so we implemented a loggingAdvice.. None of the code in our aspects are core to the functionality of our system, so it doesn't belong in our core business classes. They are aspects of our system..