Due to limitations in various programming languages, cross cutting concerns have not modularized. Cross-cutting concerns refers to parts of software that logically belong to one module and affect the whole system, this could be security, logging and others. Aspect oriented programming tries to solve these cross cutting concerns in the following way: It allows programmers to write modules called as aspects. Aspects contain pieces of code executed at particular point. The expressions required to select a particular point led to creation of Pointcut Expressions.
Execution
Whenever the programexecution reaches one of the join points described in the pointcut, a piece of code associated with the pointcut is executed. This allows a programmer to describe where and when additional code should be executed in addition to an already defined behavior. This permits the addition of aspects to existing software, or the design of software with a clear separation of concerns, wherein the programmer weaves different aspects into a complete application. Suppose there is an application where we can modify records in database. Whenever users modify the database and we want to have a log of information, regarding who is modifying the records. Traditional way to log is to call log method just before modify database method. With the Aspect oriented programming, we can apply pointcut to modify database method and have an advice that is called to log the required information.
Expressions
Some of the important Pointcut expressions supported by AspectJ. These expressions can be combined using logical operators. execution
This pointcut matches execution of Users.setPassword method. call)
When a Users.getPassword is called, this pointcut is matched. handler
Pointcut will match when there is ArrayIndexOutOfBounds exception this
Pointcut will match when object currently executing is of UserType target
Pointcut will match when target object is of UserType within
Pointcut will match when code executing belongs to UserType.
Criticisms
Pointcut languages impacts important software properties like evolvability and comprehensibility, in a negative way. There might be a possibility where there is a need to perform refactoring to define a correct aspect, which in general should not happen since refactoring is to make code cleaner. It is also not scalable when there are multiple aspects to be applied on the same code and each aspect requiring a different refactoring. In general every aspect will be tightly coupled with an application’s structure as the pointcuts explicitly contain a method’s signature. So when an application changes the pointcut needs to be changed as well. This is quite problematic for a developer.
