wicket-ear: Wicket Framework used in a WAR inside an EAR.

Demonstrates how to use the Wicket Framework 7.x with the JBoss server using the Wicket Java EE integration, packaged as an EAR

What is it?

This is an example of how to use Wicket Framework 7.x with WildFly, leveraging features of Java EE 7, using the Wicket Java EE integration.

Features used:

Injection of @PersistenceContext
Injection of a value from web.xml using @Resource
Injection of a stateless session bean using @EJB

This is an EAR version, with the following structure:

-`wicket-ear` - parent module
    - `ejb`: Contains EJB beans and JPA entities. Creates a `.jar` file
    - `war`: Contains the Wicket web application, which uses the EJB beans. Creates a `.war` file
    - `ear`: Packages the EJB JAR and WAR into an EAR. Creates an `.ear` file

System Requirements

The application this project produces is designed to be run on WildFly Application Server 13 or later.

All you need to build this project is Java 8.0 (Java SDK 1.8) or later and Maven 3.3.1 or later. See Configure Maven to Build and Deploy the Quickstarts to make sure you are configured correctly for testing the quickstarts.

Use of WILDFLY_HOME

In the following instructions, replace WILDFLY_HOME with the actual path to your WildFly installation. The installation path is described in detail here: Use of WILDFLY_HOME and JBOSS_HOME Variables.

Start the WildFly Standalone Server

Open a terminal and navigate to the root of the WildFly directory.
Start the WildFly server with the default profile by typing the following command.
```
$ WILDFLY_HOME/bin/standalone.sh 
```
Note
For Windows, use the WILDFLY_HOME\bin\standalone.bat script.

Build and Deploy the Quickstart

Make sure you start the WildFly server as described above.
Open a terminal and navigate to the root directory of this quickstart.
Type the following command to build the artifacts.
```
$ mvn clean install wildfly:deploy
```

This deploys the wildfly-wicket-ear-parent/ear/target/wildfly-wicket-ear-parent.ear to the running instance of the server.

You should see a message in the server log indicating that the archive deployed successfully.

Access the application

The application will be running at the following URL: http://localhost:8080/wildfly-wicket-ear-parent/

You will see a page with a table listing the existing Contact entities. Initially, this table is empty.
Click on the Insert a new Constact link to add a new contact.

Undeploy the Quickstart

When you are finished testing the quickstart, follow these steps to undeploy the archive.

Make sure you start the WildFly server as described above.
Open a terminal and navigate to the root directory of this quickstart.
Type this command to undeploy the archive:
```
$ mvn wildfly:undeploy
```

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 in Red Hat JBoss Developer Studio or 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 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