Red Hat

Developer Materials

payment-cdi-event: Use CDI Events to Process Debit and Credit Operations

  • Author: Elvadas Nono
  • Contributors: Sande Gilda, Pete Muir , nelvadas
  • Published: Apr 11, 2014
  • Level: Beginner
  • Technologies:CDI
  • Target Product:EAP

What is it?

This quickstart demonstrates how to use CDI 1.0 Events in Red Hat JBoss Enterprise Application Platform.

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 JBoss console and the event list is displayed in a table at the bottom of the form.

The payment-cdi-event quickstart defines the following classes:

  • PaymentBean:
    • A session scoped bean that stores the payment form information:
      • payment amount
      • operation type: debit or credit
    • It contains the following utilities methods:
      • public String pay(): Process the operation when the user clicks on submit. We have only one JSP page, so the method does not return anything and the flow of control doesn't change.
      • public void reset(): Clear the payment form data.
  • PaymentEvent: We have only one Event. It 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.
  • The qualifiers package contains the Credit and Debit classes. The annotation determines the operation of injecting Event.
  • The handler package containss 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, it implements both IcreditEventObserver and IDebitEventObserver.
    • The payment handler exposes the list of events caught during a session ( @Named name=payments).

System requirements

The application this project produces is designed to be run on Red Hat JBoss Enterprise Application Platform 6.1 or later.

All you need to build this project is Java 6.0 (Java SDK 1.6) or later, Maven 3.0 or later.

Configure Maven

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

Start the JBoss EAP Server

  1. Open a command prompt and navigate to the root of the JBoss EAP directory.
  2. The following shows the command line to start the server:

     For Linux:   EAP_HOME/bin/standalone.sh
     For Windows: EAP_HOME\bin\standalone.bat
    

Build and Deploy the Quickstart

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.

  1. Make sure you have started the JBoss EAP server as described above.
  2. Open a command prompt and navigate to the root directory of this quickstart.
  3. Type this command to build and deploy the archive:

     mvn clean install jboss-as:deploy
    
  4. This will deploy target/jboss-payment-cdi-event.war to the running instance of the server.

Access the application

The application will be running at the following URL: http://localhost:8080/jboss-payment-cdi-event/.

Undeploy the Archive

  1. Make sure you have started the JBoss EAP server as described above.
  2. Open a command prompt and navigate to the root directory of this quickstart.
  3. When you are finished testing, type this command to undeploy the archive:

     mvn jboss-as:undeploy
    

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

Recent Changelog

  • Apr 11, 2014(Sande Gilda):Bz1086883 Update Product Version metadata to include EAP 6.3
  • Mar 12, 2014(Sande Gilda):Bz1074530 replace JBOSS_HOME with EAP_HOME
  • Mar 2, 2014(Sande Gilda):Bz1025766 Replace JBoss with JBoss EAP
  • Feb 14, 2014(Sande Gilda):Replace JDBS instructions with shared resource
  • Jan 28, 2014(Sande Gilda):JDF 602 Part 2 of changes to move common instructions to a shared repository. This commit contains the Maven Configuration link changes
  • Dec 16, 2013(Sande Gilda):JDF 577 Replace command line with command prompt when referring to a terminal
  • Nov 8, 2013(Sande Gilda):Bz1028448 Add spaces to end of metadata so it renders with a line break in HTML
  • Oct 8, 2013(Sande Gilda):BZ1011833 Add HTML versions of README files and fix deployment instructions
  • Oct 2, 2013(Sande Gilda):README add Product Versions metadata remove versions in text remove temp repo from settings.xml
  • Sep 24, 2013(Sande Gilda):Remove references to web profile
Avg:
Your Rating:
×