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.
SCJA 1.0, SCJP 1.4, SCWCD 1.4, SCBCD 1.3, SCJP 5.0, SCEA 5, SCBCD 5; OCUP - Fundamental, Intermediate and Advanced; IBM Certified Solution Designer - OOAD, vUML 2; SpringSource Certified Spring Professional