What is it?
This project demonstrates how to use JPA 2.0 in JBoss Enterprise Application Platform 6 or JBoss AS 7.
It includes a persistence unit and some sample persistence code to introduce you database access in enterprise Java.
It does not contain an user interface layer. The purpose of the project is to show you how to test JPA with Arquillian.
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.
Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile
- 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
Run the Arquillian Tests
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
Run tests from JBDS
To be able to run the tests from JBDS, first set the active Maven profile in project properties to be either 'arq-jbossas-managed' for running on managed server or 'arq-jbossas-remote' for running on remote server.
To run the tests, right click on the project or individual classes and select Run As --> JUnit Test in the context menu.
Investigate the Console Output
Maven prints summary of performed tests into the console:
------------------------------------------------------- T E S T S ------------------------------------------------------- Running org.jboss.as.quickstarts.tasks.TaskDaoTest log4j:WARN No appenders could be found for logger (org.jboss.logging). log4j:WARN Please initialize the log4j system properly. Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.31 sec Running org.jboss.as.quickstarts.tasks.UserDaoTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.084 sec Results : Tests run: 8, Failures: 0, Errors: 0, Skipped: 0
SQL statements generated by Hibernate are written into the server log.
Creating the database schema:
10:16:58,770 INFO [stdout] (MSC service thread 1-2) Hibernate: create table Tasks_task (id bigint not null, title varchar(255), owner_id bigint, primary key (id)) 10:16:58,771 INFO [stdout] (MSC service thread 1-2) Hibernate: create table Tasks_user (id bigint not null, username varchar(255), primary key (id)) 10:16:58,772 INFO [stdout] (MSC service thread 1-2) Hibernate: alter table Tasks_task add constraint FKE61757B62CC79EF1 foreign key (owner_id) references Tasks_user
Generating ID for a new entity and inserting the entity into the database:
10:16:58,956 INFO [stdout] (http--127.0.0.1-8080-1) Hibernate: select tbl.next_val from hibernate_sequences tbl where tbl.sequence_name=? for update 10:16:58,957 INFO [stdout] (http--127.0.0.1-8080-1) Hibernate: insert into hibernate_sequences (sequence_name, next_val) values (?,?) 10:16:58,958 INFO [stdout] (http--127.0.0.1-8080-1) Hibernate: update hibernate_sequences set next_val=? where next_val=? and sequence_name=? 10:16:58,960 INFO [stdout] (http--127.0.0.1-8080-1) Hibernate: insert into Tasks_user (username, id) values (?, ?)
Run the Quickstart in JBoss Developer Studio or Eclipse
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
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
Find this guide useful?
FeedbackFind a bug in the guide? Something missing? You can fix it by [forking the repository](http://github.com/jboss-jdf/jboss-as-quickstart), making the correction and [sending a pull request](http://help.github.com/send-pull-requests). If you're just plain stuck, feel free to ask a question in the [user discussion forum](http://jboss.org/jdf/forums/jdf-users).
- Jun 12, 2013: Modify readme file internal links to use generated anchors. remove hard-coded anchors. fixed obsolete links and other markdown rendering problems Sande Gilda
- May 18, 2013: Fixes to problems (formatting, licensing, property names and versions, etc.) reported by the qs tools utility Sande Gilda
- Feb 12, 2013: Add quickstart source repository of record to the readme files Sande Gilda
- Sep 11, 2012: Add target product (https://issues.jboss.org/browse/jdf-108) Sande Gilda
- Jul 25, 2012: Fix #274: tasks readme is missing the step to start the server Sande Gilda
- May 18, 2012: Move metadata to quickstarts Pete Muir
- Apr 11, 2012: Remove odd trailing slashes Pete Muir
- Apr 10, 2012: Solve issue #194 :-) auto transform links from readme.md -> readme.html Pete Muir
- Apr 05, 2012: Missed adding the arquillian instructions, fixed indentations, modified jta-crash-rec and jts-distributed-crash-rec, add missing authors Sande Gilda
- Mar 26, 2012: Attempt to standardize readme.md files Sande Gilda
- Mar 20, 2012: Various Pete Muir
- Feb 29, 2012: Added information about server log contents to readme Oliver Kiss