The spring-kitchensink-basic quickstart is an example of a Java EE 7 application using JSP, JPA and Spring 4.x.
What is it?
The spring-kitchensink-basic quickstart is an example of a Java EE 7 application using JSP, JPA and Spring 4.x in WildFly Application Server. It
includes a persistence unit and some sample persistence and transaction code to introduce you to database access in enterprise Java:
-
In the
jboss-as-spring-mvc-context.xmlfile, thecontext:component-scanandmvc:annotation-drivenelements are used to register both the non-rest and rest controllers. -
The controllers map the respective urls to methods using
@RequestMapping(url). -
To return JSON, the rest controller uses
@ResponseBody. -
The datasource and entitymanager are retrieved via JNDI.
System Requirements
The application this project produces is designed to be run on WildFly Application Server 13 or later.
All you need to build this project is Java 8.0 (Java SDK 1.8) or later and Maven 3.3.1 or later. See Configure Maven to Build and Deploy the Quickstarts to make sure you are configured correctly for testing the quickstarts.
Use of WILDFLY_HOME
In the following instructions, replace WILDFLY_HOME with the actual path to your WildFly installation. The installation path is described in detail here: Use of WILDFLY_HOME and JBOSS_HOME Variables.
Start the WildFly Standalone Server
-
Open a terminal and navigate to the root of the WildFly directory.
-
Start the WildFly server with the default profile by typing the following command.
$ WILDFLY_HOME/bin/standalone.shNoteFor Windows, use the WILDFLY_HOME\bin\standalone.batscript.
Build and Deploy the Quickstart
-
Make sure you start the WildFly server as described above.
-
Open a terminal and navigate to the root directory of this quickstart.
-
Type the following command to build the artifacts.
$ mvn clean package wildfly:deploy
This deploys the spring-kitchensink-basic/target/spring-kitchensink-basic.war to the running instance of the server.
You should see a message in the server log indicating that the archive deployed successfully.
Access the application
The application will be running at the following URL: http://localhost:8080/spring-kitchensink-basic/.
Undeploy the Quickstart
When you are finished testing the quickstart, follow these steps to undeploy the archive.
-
Make sure you start the WildFly server as described above.
-
Open a terminal and navigate to the root directory of this quickstart.
-
Type this command to undeploy the archive:
$ mvn wildfly:undeploy
Run the Arquillian Functional Tests
This quickstart provides Arquillian functional tests. They are located under the functional-tests/ directory. Functional tests verify that your application behaves correctly from the user’s point of view and simulate clicking around the web page as a normal user would do.
|
Note
|
The Arquillian functional tests deploy the application, so make sure you undeploy the quickstart before you begin. |
Follow these steps to run the functional tests.
-
Start the WildFly server as described above.
-
Build the quickstart archive.
-
Open a terminal and navigate to the root directory of this quickstart.
-
Build the quickstart archive using the following command:
$ mvn clean package
-
-
Navigate to the
functional-tests/directory in this quickstart. -
Type the following command to run the
verifygoal with thearq-remoteprofile activated.$ mvn clean verify -Parq-remote
|
Note
|
You can also let Arquillian manage the WildFly server by using the |
Run the Quickstart in Red Hat JBoss Developer Studio or Eclipse
You can also start the server and deploy the quickstarts or run the Arquillian tests in Red Hat JBoss Developer Studio or from Eclipse using JBoss tools. For general information about how to import a quickstart, add a WildFly server, and build and deploy a quickstart, see Use JBoss Developer Studio or Eclipse to Run the Quickstarts.
Debug the Application
If you want to debug the source code or look at the Javadocs of any library in the project, run either of the following commands to pull them into your local repository. The IDE should then detect them.
$ mvn dependency:sources
$ mvn dependency:resolve -Dclassifier=javadoc