Skip to content

Latest commit

 

History

History
108 lines (78 loc) · 4.19 KB

README.adoc

File metadata and controls

108 lines (78 loc) · 4.19 KB
Raw

tasks-jsf: JSF, JPA quickstart

The tasks-jsf quickstart demonstrates how to use JPA persistence with JSF as the view layer.

What is it?

The tasks-jsf quickstart demonstrates how to use JPA persistence with JSF as view layer in an application deployed to WildFly Application Server. It provides a JSF front end for the tasks quickstart.

The theme of this application is simple Task management with simple login. The project contains two entities - a user and a task.

This sample includes a persistence unit and some sample persistence code to introduce you to database access in enterprise Java. Persistence code is covered by tests to help you write business logic without the need to use any view layer.

JSF is used to present the user two views.

  • authentication form: This provides the simple login

  • task view: This view contains the task list, a task detail, and a task addition form. The task view uses AJAX.

Access the Application

The application will be running at the following URL http://localhost:8080/{artifactId}/.

Server Log: Expected Warnings and Errors

You will see the following warnings in the server log. You can ignore these warnings.

WFLYJCA0091: -ds.xml file deployments are deprecated. Support may be removed in a future version.

HHH000431: Unable to determine H2 database version, certain features may not work

Run the Quickstart in Red Hat JBoss Developer Studio or Eclipse

You can also start the server and deploy the quickstarts or run the Arquillian tests from Eclipse using JBoss tools. For general information about how to import a quickstart, add a WildFly server, and build and deploy a quickstart, see Use JBoss Developer Studio or Eclipse to Run the Quickstarts.

Debug the Application

If you want to debug the source code of any library in the project, run the following command to pull the source into your local repository. The IDE should then detect it.

$ mvn dependency:sources