Aspect Oriented Programming with Spring AspectJ Part2

Let's recap a few things about the Maven Web project structure

1. /src/main/java folder contains source files for the dynamic content of the application
2. /src/test/java folder contains all source files for unit tests
3. /src/main/webapp folder contains essential files for creating a valid web application, e.g. „web.xml“
4. /target folder contains the compiled and packaged deliverables
5. The „pom.xml“ is the project object model (POM) file. The single file that contains all project related configuration.

In order to properly use Spring at runtime, we must provide all necessary libraries to the web application. Open the graphical editor of your „pom.xml“ and perform the following changes :

1. Locate the „Properties“ section at the „Overview“ page of the POM editor and perform the following changes :
• Create a new property with name org.springframework.version and value3.0.1.RELEASE
• Create a new property with name maven.compiler.source and value according to the version of your Java runtime environment, we will use 1.6
• Create a new property with name maven.compiler.target and value according to the version of your Java runtime environment, we will use 1.6
2. Navigate to the „Dependencies“ page of the POM editor and create the following dependencies (you should fill the „GroupId“, „Artifact Id“ and „Version“ fields of the „Dependency Details“ section at that page) :
• Group Id : org.springframework Artifact Id : spring-web Version :${org.springframework.version}
• Group Id : org.aspectj Artifact Id : aspectjrt Version : 1.6.7
3. Navigate to the “Plugins” page of the POM editor and create the following plugin (you should fill the „GroupId“, „Artifact Id“ and „Version“ fields of the „Plugin Details“ section at that page) :
• Group Id : org.codehaus.mojo Artifact Id : aspectj-maven-plugin Version : 1.3
4. At the “Plugins” page of the POM editor, select the newly created plugin (from the “Plugins” section), and bind it to the compile execution goal. To do so, locate the “Execution” section and create a new execution. At the “Execution Details” section create a new goal and name it “compile”
5. The newly created plugin needs one final configuration change. We must define what version of Java runtime environment we are using in order for the AspectJ compiler to properly weave aspect classes. We need to edit the “pom.xml” file to perform the change. Select the “pom.xml” page of the POM editor, locate the newly created plugin and alter it as follows :

01

<plugin>

02	<groupId>org.codehaus.mojogroupId>

03	<artifactId>aspectj-maven-pluginartifactId>

04	<version>1.3version>

05	<configuration>

06	<source>${maven.compiler.source}source>

07	<target>${maven.compiler.target}target>

08	configuration>

09	<executions>

10	<execution>

11

<goals>

12	<goal>compilegoal>

13

goals>

14	execution>

15	executions>

16

plugin>

6. Finally change the “maven-compiler-plugin” as shown below :

1

<plugin>

2	<groupId>org.apache.maven.pluginsgroupId>

3	<artifactId>maven-compiler-pluginartifactId>

4	<version>2.0.2version>

5	<configuration>

6	<source>${maven.compiler.source}source>

7	<target>${maven.compiler.target}target>

8	configuration>

9

plugin>

As you can see Maven manages library dependencies declaratively. A local repository is created (by default under {user_home}/.m2 folder) and all required libraries are downloaded and placed there from public repositories. Furthermore intra – library dependencies are automatically resolved and manipulated.