Demonstrates how to use the Wicket Framework 7.x with the JBoss server using the Wicket Java EE integration packaged as a WAR
This is an example of how to use Wicket Framework 7.x with WildFly, leveraging features of Java EE 7, using the Wicket-Stuff 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 a WAR version.
All you need to build this project is Java 8 (Java SDK 1.8) or better, Maven 3.1 or better.
The application this project produces is designed to be run on JBoss WildFly.
If you have not yet done so, you must Configure Maven before testing the quickstarts.
-
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
NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See Build and Deploy the Quickstarts 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 this command to build and deploy the archive:
mvn clean package wildfly:deploy
.
This will deploy target/wildfly-wicket-war.war
to the running instance of the server.
Access the running application in a browser at the following URL: http://localhost:8080/wildfly-wicket-war
You will see a page with a table listing user entities. Initially, this table is empty. By clicking a link, you can add more users.
-
Make sure you have started the JBoss Server as described above.
-
Open a command line and navigate to the root directory of this quickstart. .
When you are finished testing, type this command to undeploy the archive:
mvn wildfly:undeploy