Author: Paul Robinson Level: Intermediate Technologies: EJB, JSF, WAR Summary: Packages an EJB JAR in a WAR
This example demonstrates the deployment of an EJB 3.1 bean bundled in a war archive for deployment to JBoss Enterprise Application Platform 6 or JBoss AS 7. The project also includes a set of Aquillian tests for the managed bean and EJB.
The example follows the common "Hello World" pattern. These are the steps that occur:
- A JSF page asks the user for their name.
- On clicking submit, the name is sent to a managed bean namde
Greeter
. - On setting the name, the
Greeter
invokes theGreeterEJB
, which was injected into the managed bean. Notice the field annotated with@EJB
. - The response from invoking the
GreeterEJB
is stored in a fieldmessage
of the managed bean. - The managed bean is annotated as
@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.
All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven 3.0 or better.
The application this project produces is designed to be run on JBoss Enterprise Application Platform 6 or JBoss AS 7.
If you have not yet done so, you must Configure Maven before testing the quickstarts.
-
Open a command line and navigate to the root of the JBoss server directory.
-
The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh For Windows: JBOSS_HOME\bin\standalone.bat
NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See Build and Deploy the Quickstarts for complete instructions and additional options.
-
Make sure you have started the JBoss Server as described above.
-
Open a command line and navigate to the root directory of this quickstart.
-
Type this command to build and deploy the archive:
mvn clean package jboss-as:deploy
-
This will deploy
target/jboss-as-ejb-in-war.war
to the running instance of the server.
The application will be running at the following URL http://localhost:8080/jboss-as-ejb-in-war.
-
Make sure you have started the JBoss Server as described above.
-
Open a command line and navigate to the root directory of this quickstart.
-
When you are finished testing, type this command to undeploy the archive:
mvn jboss-as:undeploy
This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container.
NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See Run the Arquillian Tests for complete instructions and additional options.
-
Make sure you have started the JBoss Server as described above.
-
Open a command line and navigate to the root directory of this quickstart.
-
Type the following command to run the test goal with the following profile activated:
mvn clean test -Parq-jbossas-remote
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:
[timestamp] INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "test.war"
...
[timestamp] INFO [org.jboss.as.server] (management-handler-thread - 7) JBAS018559: Deployed "test.war"
...
[timestamp] INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment test.war in 51ms
...
[timestamp] INFO [org.jboss.as.server] (management-handler-thread - 5) JBAS018558: Undeployed "test.war"
You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see Use JBoss Developer Studio or Eclipse to Run the Quickstarts
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