Home > Tutorials > Struts 2 + Spring 2 + JPA + AJAX |
On this tutorial we will demonstrate how to setup Struts 2 in Eclipse, and make it work with Spring, Java Persistence API (using Hibernate) and Struts 2 Ajax tags.
Install Tomcat before going forward. See Tomcat's installation guide if you have any problem installing it.
Install and configure MySql. Create a database named "quickstart" and run the script below to create the "Person" table. Later, on applicationContext.xml, we'll use 'root' as the user name and password for the database, remember to replace those values with the right ones for your database.
You can just download the zipped Eclipse project, add the required dependencies to the lib folder under the /WebContent/WEB-INF/lib folder (relative to project's root folder) and import it into Eclipse.
To run the project this way you will need maven installed.
Your project should contain the folders "src", "build" and "WebContent". We are going to put all the required jars under "/WebContent/WEB-INF/lib". To add files to the "lib" folder, just copy them to ${workspace}\quickstart\WebContent\WEB-INF\lib, where ${workspace} is the location of your Eclipse workspace folder.
In the table, the version has been removed from the JAR files, since these may change in future milestone releases. Use whatever version is shipping with the indicated products.
JAR | From | License |
---|---|---|
xwork.jar | ||
struts2-core.jar | Struts 2 | |
struts2-spring-plugin.jar | Struts 2 | |
ognl.jar | Struts 2 | |
freemarker.jar | Struts 2 | |
commons-logging-api.jar | Struts 2 | |
mysql-connector-java.jar | ||
spring.jar | ||
antlr.jar | ||
asm.jar | Hibernate Core | |
asm-attrs.jar | Hibernate Core | |
cglib.jar | Hibernate Core | |
dom4j.jar | Hibernate Core | |
jdbc2_0-stdext.jar | Hibernate Core | |
ehcache.jar | Hibernate Core | |
hibernate3.jar | Hibernate Core | |
xml-apis.jar | Hibernate Core | |
commons-collections.jar | Hibernate Core | |
ejb3-persistence.jar | ||
jta.jar | Hibernate Annotations | |
hibernate-commons-annotations.jar | Hibernate Annotations | |
hibernate-annotations.jar | Hibernate Annotations | |
hibernate-entitymanager.jar | ||
javassist.jar | Hibernate Entity Manager | |
jboss-archive-browsing.jar | Hibernate Entity Manager |
Right click on the project and select "Refresh" (to notify Eclipse of the jars that we just added).
Our domain model will consist of just a simple "Person" class with a couple of fields.
your class will look like:
@Entity will let the provider know that this class can be persisted. @Id marks the "id" field as the primary key for this class. @GeneratedValue will cause the id field to be generated by the provider (Hibernate). Classes and fields are by default mapped to tables and columns with the same name, see JPA's documentation for more details.
We will now write the class that will take care of CRUD operations on "Person" objects.
@PersistenceContext will make Spring inject an EntityManager into the service when it is instantiated. The @PersistenceContext annotation can be placed on the field, or on the setter method. If the class is annotated as @Transactional, Spring will make sure that its methods run inside a transaction.
JPA configuration can be set on this file. On this example it will be empty because the datasource configuration will be in the Spring configuration file.
This will make the container redirect all requests to Struts "FilterDispatcher" class. "index.jsp" is set as the home page, and Spring's "ContextLoaderListener" is configured as a listener.
Note that the "class" attribute of the bean "personAction" is set to the name of the action class, and the "personService" bean will be passed as a parameter to the action constructor. Change the "url", "username" and "password" in the "dataSource" bean to the appropiate values for your database. For more details on the rest of the beans on this file, see Spring's documentation. The "scope" attribute is new in Spring 2, and it means that Spring will create a new PersonAction object every time an object of that type is requested. In Struts 2 a new action object is created to serve each request, that's why we need scope="prototype".
We will now create a simple Struts action that wraps PersonServices methods, and we will configure Struts to use Spring as the object factory.
Look mom my action is a simple POJO!
The "Preparable" interface instructs Struts to call the "prepare" method if the "PrepareInterceptor" is applied to the action (by default, it is). The constructor of the action takes a "PersonService" as a parameter, which Spring will take care of passing when the action is instatiated.
Setting "struts.objectFactory" to "spring" will force Struts to instantiate the actions using Spring, injecting all the defined dependencies on applicationContext.xml. The "class" attribute for each action alias is set to "personAction", which is the bean id that we defined on applicationContext.xml for the PersonAction class. This is all that is needed to make Struts work with Spring.
We only have two pages, "index.jsp" and "list.jsp". "list.jsp" returns a table with a list of the persons on the database.We have this list on a different page because we are going to add some AJAX to spicy it up.
This is going to render a table with each row showing the first and last name of the person, a link to remove the person, and a link to edit. The remove link has the attribute "targets", set to "persons", which means that when the user clicks on it, an asynchronous request will be made to the "remove" action (as configured on struts.xml, "remove" points to the "remove" method in PersonAction), passing the person id as parameter.
When the edit link is clicked on, it will publish the "/edit" topic, which will trigger a javascript function to populate the fields.
Look mom no page refresh!
The div "persons" will load its content asynchronously, and will show "Loading..." while while the request is on progress (you can use the "indicator" attribute for better progress feedback), you can force it to refresh clicking on the "Refresh" link. The "submit" button, will make an asynchronous request to the action "save" ("save" method on PersonAction), and will publish the topic "/save" to which we subscribed to, using "dojo.event.topic.subscribe", to clear the input fields.
Because we don't want any John Doe on our database, we will add some basic client side validation to our form. In Struts 2, validation can be placed on xml files with the name pattern ActionName-validation.xml, located on the same package as the action. To add validation to an specific alias of an action (like a method), the validation file name follows the pattern ActionName-alias-validation.xml, where "alias" is the action alias name (in this case a method name, "save"). Add a file named "PersonAction-save-validation.xml" under /src/quickstart/action, and set its content to:
See the Struts documentation for details on existing validators, and how to write, and plug in, your own validators.
To run the project, Right click on your project and Run As -> Run on Server. You can debug it on the same way, Right click on the project and Debug As -> Debug on Server. Download and install Struts 2 Showcase to see more examples.