Author: Pete Muir Level: Intermediate Technologies: EAR Summary: Based on kitchensink, but deployed as an EAR Target Product: EAP Source: https://github.com/jboss-jdf/jboss-as-quickstart/
This is your project! It is a sample, deployable Maven 3 project to help you get your foot in the door developing with Java EE 6 on JBoss Enterprise Application Platform 6 or JBoss AS 7.
This project is setup to allow you to create a compliant Java EE 6 application using JSF 2.0, CDI 1.0, EJB 3.1, JPA 2.0 and Bean Validation 1.0. It includes a persistence unit and some sample persistence and transaction code to introduce you to database access in enterprise Java.
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.
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/brewz.ear
to the running instance of the server.
The application will be running at the following URL: http://localhost:8080/brewz-web.
When the registration is successful, you will see a log message in the server console:
Registering _the_name_you_entered_
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.
Type the following command to run the test goal with the following profile activated:
mvn clean test -Parq-jbossas-remote
You should see the following console output when you run the tests:
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
You should see messages similar to the following:
INFO [org.jboss.as.server] (management-handler-thread - 9) JBAS018559: Deployed "test.war"
INFO [org.zajac.brewz.controller.MemberRegistration] (http--127.0.0.1-8080-2) Registering Jane Doe
INFO [org.zajac.brewz.test.MemberRegistrationTest] (http--127.0.0.1-8080-2) Jane Doe was persisted with id 1
INFO [org.jboss.weld.deployer] (MSC service thread 1-6) JBAS016009: Stopping weld service for deployment test.war
INFO [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011403: Stopping Persistence Unit Service 'test.war#primary'
INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-1) HHH000227: Running hbm2ddl schema export
INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-1) HHH000230: Schema export complete
INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) JBAS010409: Unbound data source [jboss/datasources/brewzTestDS]
INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015877: Stopped deployment test.war in 19ms
INFO [org.jboss.as.server] (management-handler-thread - 10) 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