Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Fetching latest commit...
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.

tasks: Testing JPA with Arquillian

Authors: Oliver Kiss and Lukas Fryc

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.

System requirements

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.

Configure Maven

If you have not yet done so, you must Configure Maven before testing the quickstarts.

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.

  1. Make sure you have started the JBoss Server as described above.
  2. Open a command line and navigate to the root directory of this quickstart.
  3. 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
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
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.084 sec

Results :

Tests run: 8, Failures: 0, Errors: 0, Skipped: 0

Server log

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-- Hibernate: select tbl.next_val from hibernate_sequences tbl where tbl.sequence_name=? for update
10:16:58,957 INFO  [stdout] (http-- Hibernate: insert into hibernate_sequences (sequence_name, next_val)  values (?,?)
10:16:58,958 INFO  [stdout] (http-- Hibernate: update hibernate_sequences set next_val=?  where next_val=? and sequence_name=?
10:16:58,960 INFO  [stdout] (http-- 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
Something went wrong with that request. Please try again.