The spring-greeter quickstart is based on the greeter quickstart, but differs in that it uses Spring MVC for Mapping GET and POST requests.

What is it?

The application this project produces is designed to be run on WildFly Application Server 13 or later.

The spring-greeter quickstart is based on the greeter quickstart, but differs in that it uses Spring MVC for Mapping GET and POST requests:

  • The mvc:annotation-driven element configured in the src/main/webapp/WEB-INF/spring-mvc-context.xml file tells Spring to look for @RequestMapping in the controllers.

  • Spring then routes the HTTP requests to the correct methods in CreateController.java and GreetController

Spring’s XML configurations are used to get hold of the database and entity manager (via jndi) to perform transactional operations:

  • The tx:jta-transaction-manager and tx:annotation-driven elements are configured in the /src/main/webapp/WEB-INF/spring-business-context.xml file.

  • Methods in UserDaoImpl are marked as @Transactional, which Spring, using aspect oriented programming, surrounds with boilerplate code to make the methods transactional

When you deploy this example, two users are automatically created for you: emuster and jdoe. This data is located in the src/main/resources/init-db.sql file.

To test this example:

  1. Enter a name in the username field and click on Greet!.

  2. If you enter a username that is not in the database, you get a message No such user exists!`.

  3. If you enter a valid username, you get a message "Hello, " followed by the user’s first and last name.

  4. To create a new user, click the Add a new user link. Enter the username, first name, and last name, and then click Add User. The user is added and a message displays the new user ID number.

  5. Click on the Greet a user! link to return to the Greet! page.

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

  1. Open a terminal and navigate to the root of the WildFly directory.

  2. Start the WildFly server with the default profile by typing the following command.

    $ WILDFLY_HOME/bin/standalone.sh
    Note
    		 For Windows, use the WILDFLY_HOME\bin\standalone.bat script.

Build and Deploy the Quickstart

  1. Make sure you start the WildFly server as described above.

  2. Open a terminal and navigate to the root directory of this quickstart.

  3. Type the following command to build the artifacts.

    $ mvn clean package wildfly:deploy

This deploys the spring-greeter/target/spring-greeter.war to the running instance of the server.

You should see a message in the server log indicating that the archive deployed successfully.

If you do not have Maven configured you can manually copy target/spring-greeter.war to WILDFLY_HOME/standalone/deployments/ directory.

Access the application

The application will be running at the following URL: http://localhost:8080/spring-greeter/

Undeploy the Quickstart

When you are finished testing the quickstart, follow these steps to undeploy the archive.

  1. Make sure you start the WildFly server as described above.

  2. Open a terminal and navigate to the root directory of this quickstart.

  3. Type this command to undeploy the archive:

    $ mvn wildfly:undeploy

Or you can manually remove the application by removing spring-greeter.war from the WILDFLY_HOME/standalone/deployments/ directory.

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.

  1. Start the WildFly server as described above.

  2. Build the quickstart archive.

    1. Open a terminal and navigate to the root directory of this quickstart.

    2. Build the quickstart archive using the following command:

      $ mvn clean package

  3. Navigate to the functional-tests/ directory in this quickstart.

  4. Type the following command to run the verify goal with the arq-remote profile activated.

    $ mvn clean verify -Parq-remote
Note

You can also let Arquillian manage the WildFly server by using the arq-managed profile, meaning the tests will start the server for you. This profile requires that you provide Arquillian with the location of the WildFly server, either by setting the JBOSS_HOME environment variable, or by setting the jbossHome property in the arquillian.xml file. For more information, see Run the Arquillian Tests.

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