Author: Elvadas Nono
Level: Beginner
Technologies: CDI, JSF
Summary: The payment-cdi-event
quickstart demonstrates how to create credit and debit CDI Events in WildFly, using a JSF front-end client.
Target Product: WildFly
Source: https://github.com/wildfly/quickstart/
The payment-cdi-event
quickstart demonstrates how to use CDI Events in WildFly Application Server.
The JSF front-end client allows you to create both credit and debit operation events.
To test this quickstart, enter an amount, choose either a Credit or Debit operation, and then click on Pay to create the event.
A Session scoped (@SessionScoped
) payment event handler catches the operation and produces (@Produces
) a named list of all operations performed during this session. The event is logged in the WildFly server log and the event list is displayed in a table at the bottom of the form.
The payment-cdi-event
quickstart defines the following classes and interfaces:
beans
package contains the PaymentBean
bean class:private void init()
: This is a PostConstruct (@PostConstruct
) method that performs initialization before the class is put into service. It resets the amount
to $0
and the paymentOption
to the default type of debit.public String pay()
: This method processes the operation when the user clicks on submit. We have only one JSF page, so the method does not return anything and the flow of control does not change.public void reset()
: Reset calls the init()
method reinitialize the form values.events
package contains the PaymentEvent
class and the enum PaymentTypeEnum
.PaymentEvent
: We have only one event that handles both credit and debit operations. Qualifiers help us to make the difference at injection point.PaymentTypeEnum
: A typesafe enum is used to represent the operation payment type. It contains utility methods to convert between String
and Enum
.qualifiers
package contains the Credit
and Debit
interfaces. The annotation determines the operation of the injecting Event
.handler
package contains interfaces and implementations of PaymentEvent
observers.ICreditEventObserver
: Interface to listen to CREDIT
event only (@Observes
@Credit
).IDebitEventObserver
: Interface to listen to DEBIT
event (@Observes
@Debit
).PaymentHandler
: The concrete implementation of the payment handler.
ICreditEventObserver
and IDebitEventObserver
.@Named
name=payments
).resources
package contains the Resources
class that produces the logger for the application.The application this project produces is designed to be run on WildFly Application Server 11 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 for WildFly 11 to make sure you are configured correctly for testing the quickstarts.
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.
For Linux: WILDFLY_HOME/bin/standalone.sh
For Windows: WILDFLY_HOME\bin\standalone.bat
mvn clean install wildfly:deploy
This will deploy target/payment-cdi-event.war
to the running instance of the server.
The application will be running at the following URL: http://localhost:8080/payment-cdi-event/.
mvn wildfly:undeploy
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.
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