Basically, this is not that different than if the question were to be change to "Why shouldn't we use Java/OOP?".
Ramnivas Laddad wrote:AOP actually reduces technical complexity
I don't see how it reduce technical complexity.
For example, if we don't use AOP and want to do logging, the code will be very simple (actually it's simplest):
Technically, it's simplest, developers don't need to know anything except method invocation. But if we use AOP the code will become:
We have to create aspect, define advice, pointcut. Developers need to understand what is aspect, advice, pointcut, etc. This clearly adds more complexity to the project, and adds more things developers need to know.
Surely, AOP can be learned, but I'm interested about what is the point that even if it adds more complexity it's justified to use AOP.
John Grath wrote:Hi. This looks like an old post. Spring 2.5+ handles this rather well.
Like everything in Spring you need to learn it before it becomes easy. I think Aspects are very useful in Spring and worth learning.
Yes, this is an old post. So I am going to close it so it isn't resurrrected again. ;)