Skip to content

Latest commit

 

History

History
106 lines (65 loc) · 4.95 KB

README.md

File metadata and controls

106 lines (65 loc) · 4.95 KB
Raw

carmart-tx: Example Using Local Infinispan Cache and Transactions

Author: Martin Gencur, Tristan Tarrant Level: Intermediate Technologies: Infinispan, CDI, Transactions Summary: The carmart-tx quickstart demonstrates how to configure and access Infinispan cache within a transaction, in a simple web application. Target Product: JDG Product Versions: JDG 7.x, EAP 7.x Source: https://github.com/infinispan/jdg-quickstart

What is it?

The carmart-tx is a simple web application that uses Infinispan instead of a relational database.

Users can list cars, add new cars or remove them from the CarMart. Information about each car is stored in a cache. The application also shows cache statistics like stores, hits, retrievals, etc.

The Transactional CarMart quickstart works only in a library mode", so the application has a slightly different architecture". All libraries (jar files) are bundled with the application and deployed to the server. Caches are configured programmatically and run in the same JVM as the web application.

All operations are done in a transactional context that is configured at JBossASCacheContainerProvider/TomcatCacheContainerProvider impl classes for CacheContainerProvider interface.

Infinispan ships with several transaction manager lookup classes:

  • DummyTransactionManagerLookup : This provides with a dummy transaction manager which should only be used for testing. Being a dummy, this is not recommended for production use a it has some severe limitations to do with concurrent transactions and recovery.
  • JBossStandaloneJTAManagerLookup : If you're running Infinispan in a standalone environment, this should be your default choice for transaction manager. It's a fully fledged transaction manager based on JBoss Transactions which overcomes all the deficiencies of the dummy transaction manager.
  • GenericTransactionManagerLookup : This is a lookup class that locate transaction managers in the most popular Java EE application servers (JBoss, JRun4, Resin, Orion, JOnAS, BEA Weblogic, Websphere, Glassfish). If no transaction manager can be found, it defaults on the dummy transaction manager.
  • JBossTransactionManagerLookup : This lookup class locates the transaction manager running within a JBoss Application Server instance.

System requirements

All you need to build this project is Java 8.0 (Java SDK 1.8) or better, Maven 3.0 or better.

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

Configure Maven

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

Start EAP

  1. Open a command line and navigate to the root of the EAP server directory.

  2. 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

Build and Deploy the Application in Library Mode

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 the main README for more information.

  1. Make sure you have started EAP as described above.

  2. Open a command line and navigate to the root directory of this quickstart.

  3. Type this command to build and deploy the archive:

     mvn clean package wildfly:deploy

  4. This will deploy target/jboss-carmart-tx.war to the running instance of the server.

Access the application

Access the running application in a browser at the following URL: http://localhost:8080/jboss-carmart-tx/

Undeploy the Archive

  1. Make sure you have started EAP as described above.

  2. Open a command line and navigate to the root directory of this quickstart.

  3. When you are finished testing, type this command to undeploy the archive:

     mvn wildfly:undeploy

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

Test the Application

If you want to test the application, there are simple Arquillian Selenium tests prepared. To run these tests on EAP:

  1. Stop EAP (if you have one running)

  2. Open a command line and navigate to the root directory of this quickstart.

  3. Build the quickstart using:

     mvn clean package

  4. Type this command to run the tests:

     mvn test -Puitests-eap -DeapHome=/path/to/server