Skip to main content

AOP - Aspect Oriented programming

Advice: An aspect's functionality. Aspects have a purpose - a job they're meant to do. In AOP terms, the job of an aspect is called advice. Advice  is woven into a program's execution at one or more join points.

Advice defines both the what and the when of an aspect. Spring aspects can work with five kinds of advice:
 Before—The advice functionality takes place before the advised method is
 After—The advice functionality takes place after the advised method completes,
regardless of the outcome.
 After-returning—The advice functionality takes place after the advised method
successfully completes.
 After-throwing—The advice functionality takes place after the advised method
throws an exception.
 Around—The advice wraps the advised method, providing some functionality
before and after the advised method is invoked.

"execution(* com.springinaction.springidol.Performer.perform(..))"
method="takeSeats" />
method="applaud" />
method="demandRefund" />

Join Points,
A join point is a point in the execution of the application where an aspect can be plugged in. This point could be a method being called, an exception being thrown, or even a field being modified.


If advice defines the what and when of aspects, then pointcuts define the where. A
pointcut definition matches one or more join points at which advice should be woven.

An aspect is the merger of advice and pointcuts. Taken together, advice and pointcuts define everything there is to know about an aspect - what it does and where an when it does it.

An introduction allows you to add new methods or attributes to existing classes.

Weaving is the process of applying aspects to a target object to create a new proxied object. Spring Aspects are woven in sometime during the execution of the application. Typically, Spring AOP Container will dynamically generate a proxy object that will delegate to the target object while weaving in the aspect in Runtime.

Annotating aspects,
A key feature introduced in ApsectJ5 is the ability to use annotations to create aspects.
Prerequisite:  <aop:aspectj-autoproxy/>

public classAudience{
"execution(* com.springinaction.springidol.Performer.perform(..))")
public voidperformance(){
public voidtakeSeats(){
public voidturnOffCellPhones(){
public voidapplaud(){
public voiddemandRefund(){


Popular posts from this blog

Stretch a row if data overflows in jasper reports

It is very common that some columns of the report need to stretch to show all the content in that column. But  if you just specify the property " stretch with overflow' to that column(we called text field in jasper report world) , it will just stretch that column and won't change other columns, so the row could be ridiculous. Haven't find the solution from internet yet. So I just review the properties in iReport one by one and find two useful properties(the bold highlighted in example below) which resolve the problems.   example:
<band height="20" splitType="Stretch"> <textField isStretchWithOverflow="true" pattern="" isBlankWhenNull="true"> <reportElement stretchType="RelativeToTallestObject" mode="Opaque" x="192" y="0" width="183" height="20"/> <box leftPadding="2"> <pen lineWidth="0.25"/> …

JasperReports - Configuration Reference

Spring - Operations with jdbcTemplate

This class manages all the database communication and exception handling using a java.sql.Connection that is obtained from the provided DataSource. JdbcTemplate is a stateless and threadsafe class and you can safely instantiate a single instance to be used for each DAO.

Use of Callback Methods
JdbcTemplate is based on a template style of programming common to many other parts of Spring. Some method calls are handled entirely by the JdbcTemplate, while others require the calling class to provide callback methods that contain the implementation for parts of the JDBC workflow. This is another form of Inversion of Control. Your application code hands over the responsibility of managing the database access to the template class. The template class in turn calls back to your application code when it needs some detail processing filled in. These callback methods are allowed to throw a java.sql.SQLException, since the framework will be able to catch this exception and use its built-in excepti…