Author: Paul Robinson
Level: Intermediate
Technologies: EJB, JSF, WAR
Summary: The ejb-in-war
quickstart demonstrates how to package an EJB bean in a WAR archive and deploy it to WildFly. Arquillian tests are also provided.
Target Product: WildFly
Source: https://github.com/wildfly/quickstart/
The ejb-in-war
quickstart demonstrates the deployment of an EJB bean bundled in a WAR archive for deployment to WildFly Application Server. The project also includes a set of Arquillian tests for the managed bean and EJB.
The example follows the common "Hello World" pattern. These are the steps that occur:
Greeter
.Greeter
invokes the GreeterEJB
, which was injected into the managed bean. Notice the field annotated with @EJB
.GreeterEJB
is stored in a field message
of the managed bean.@SessionScoped
, so the same managed bean instance is used for the entire session. This ensures that the message is available when the page reloads and is displayed to the user.The application this project produces is designed to be run on WildFly Application Server 11 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 for WildFly 11 to make sure you are configured correctly for testing the quickstarts.
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.
For Linux: WILDFLY_HOME/bin/standalone.sh
For Windows: WILDFLY_HOME\bin\standalone.bat
mvn clean install wildfly:deploy
This will deploy target/ejb-in-war.war
to the running instance of the server.
The application will be running at the following URL http://localhost:8080/ejb-in-war/.
mvn wildfly:undeploy
This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container.
mvn clean verify -Parq-remote
You can also let Arquillian manage the WildFly server by using the arq-managed
profile. For more information about how to run the Arquillian tests, see Run the Arquillian Tests.
JUnit will present you test report summary:
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
If you are interested in more details, check target/surefire-reports
directory. You can check console output to verify that Arquillian has really used the real application server. Search for lines similar to the following ones in the server output log:
INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war")
...
INFO [org.jboss.as.server] (management-handler-thread - 29) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war")
...
INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 12ms
...
INFO [org.jboss.as.server] (management-handler-thread - 30) WFLYSRV0009: Undeployed "test.war" (runtime-name: "test.war")
You can also start the server and deploy the quickstarts or run the Arquillian tests 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.
If you want to debug the source code of any library in the project, run the following command to pull the source into your local repository. The IDE should then detect it.
mvn dependency:sources