- Notifications
You must be signed in to change notification settings - Fork1
UFMT/periscope
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
This is your project! It's a sample, deployable Maven 3 project to help youget your foot in the door developing with Java EE 6 on JBoss AS 7. Thisproject is setup to allow you to create a compliant Java EE 6 applicationusing JSF 2.0, CDI 1.0, EJB 3.1, JPA 2.0 and Bean Validation 1.0. It includesa persistence unit and some sample persistence and transaction code to helpyou get your feet wet with database access in enterprise Java.
All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven3.0 or better.
The application this project produces is designed to be run on a JBoss AS 7.
NOTE:This project some retrieves artifacts from the JBoss Community Maven repository.
With the prerequisites out of the way, you're ready to build and deploy.
First you need to start JBoss AS 7. To do this, run
$JBOSS_HOME/bin/standalone.sh
or if you are using windows
$JBOSS_HOME/bin/standalone.bat
To deploy the application, you first need to produce the archive to deploy usingthe following Maven goal:
mvn package
You can now deploy the artifact to JBoss AS by executing the following command:
mvn jboss-as:deploy
This will deploytarget/periscope.ear
.
The application will be running at the following URLhttp://localhost:8080/periscope/.
To undeploy from JBoss AS, run this command:
mvn jboss-as:undeploy
You can also start JBoss AS 7 and deploy the project using Eclipse. See the JBoss AS 7Getting Started Guide for Developers for more information.
By default, tests are configured to be skipped. The reason is that the sampletest is an Arquillian test, which requires the use of a container. You canactivate this test by selecting one of the container configuration providedfor JBoss AS 7 (remote).
To run the test in JBoss AS 7, first start a JBoss AS 7 instance. Then, run thetest goal with the following profile activated:
mvn clean test -Parq-jbossas-remote
If you created the project using the Maven archetype wizard in your IDE(Eclipse, NetBeans or IntelliJ IDEA), then there is nothing to do. You shouldalready have an IDE project.
If you created the project from the commandline using archetype:generate, thenyou need to import the project into your IDE. If you are using NetBeans 6.8 orIntelliJ IDEA 9, then all you have to do is open the project as an existingproject. Both of these IDEs recognize Maven projects natively.
Detailed instructions for using Eclipse with JBoss AS 7 are provided in theJBoss AS 7 Getting Started Guide for Developers.
If you want to be able to debug into the source code or look at the Javadocsof any library in the project, you can run either of the following twocommands to pull them into your local repository. The IDE should then detectthem.
mvn dependency:sourcesmvn dependency:resolve -Dclassifier=javadoc