This is a fork of jboss-developer/ticket-monster. This repo only contains the demo folder of the original repo at https://github.com/jboss-developer/ticket-monster/tree/WFLY8.1/demo Furthermore it only contains the WFLY8.1 branch.

TicketMonster is an online ticketing demo application that gets you started with JBoss technologies, and helps you learn and evaluate them.

Here are a few instructions for building and running it. You can learn more about the example from the tutorial.

NOTE: This step is optional. It is necessary only if you want to update the dates of the Performances in the import.sql script in an automated manner. Updating the performance dates ensure that they are always set to some timestamp in the future, and ensures that all performances are visible in the Monitor section of the TicketMonster application.

1. Run the update_import_sql Perl script. You'll need the DateTime, DateTime::Format::Strptime and Tie::File Perl modules. These are usually available by default in your Perl installation.

    $ perl update_import_sql.pl src/main/resources/import.sql
   

NOTE: This step is optional. The administration site is already present in the source code. If you want to regenerate it from Forge, and apply the changes outlined in the tutorial, you may continue to follow the steps outlined here. Otherwise, you can skip this step and proceed to build TicketMonster.

Before building and running TicketMonster, you must generate the administration site with Forge.

1. Ensure that you have JBoss Forge installed. The current version of TicketMonster supports version 2.6.0.Final or higher of JBoss Forge. JBoss Developer Studio 8 is recommended, since it contains JBoss Forge 2 with all the necessary plugins for the TicketMonster app.

2. Start the JBoss Forge console in JBoss Developer Studio. This can be done from the Forge Console view. If the view is not already visible, it can be opened through the 'Window' menu: Window -> Show View -> Other.... Select the 'Forge Console' item in the dialog to open the Forge Console. Click the Start button in the Forge Console tab, to start Forge.

3. From the JBoss Forge prompt, browse to the 'demo' directory of the TicketMonster sources and execute the script for generating the administration site

    $ cd ticket-monster/demo
    $ run admin_layer.fsh
   

   The git patches need to be applied manually. Both the patches are located in the patches sub-directory. To apply the manual changes, first apply the patch located in file admin_layer_functional.patch. Then perform the same for the file admin_layer_graphics.patch if you want to apply the style changes for the generated administration site. You can do so in JBoss Developer Studio, by opening the context-menu on the project (Right-click on the project) and then apply a git patch via Team -> Apply Patch.... Locate the patch file in the Workspace, select it and click the 'Next' button. In the next dialog, select to apply the patch on the 'ticket-monster' project in the workspace. Click Finish in the final page of the wizard after satisfying that the patch applies cleanly.

4. Deployment to JBoss EAP 6.2 is optional. The project can be built and deployed to a running instance of JBoss EAP through the following command in JBoss Forge:

    $ build clean package jboss-as:deploy
   

TicketMonster can be built from Maven, by runnning the following Maven command:

mvn clean package

If you want to run the Arquillian tests as part of the build, you can enable one of the two available Arquillian profiles.

For running the tests in an already running application server instance, use the arq-jbossas-remote profile.

mvn clean package -Parq-jbossas-remote

If you want the test runner to start an application server instance, use the arq-jbossas-managed profile. You must set up the JBOSS_HOME property to point to the server location, or update the src/main/test/resources/arquillian.xml file.

mvn clean package -Parq-jbossas-managed

If you intend to deploy into OpenShift, you can use the postgresql-openshift profile

mvn clean package -Ppostgresql-openshift

If you intend to deploy into OpenShift, you can use the mysql-openshift profile

mvn clean package -Pmysql-openshift

You can run TicketMonster into a local JBoss EAP 6.2 instance or on OpenShift.

1. Open a command line and navigate to the root of the JBoss 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
   

1. Make sure you have started the JBoss Server as described above.

2. Type this command to build and deploy the archive into a running server instance.

    mvn clean package jboss-as:deploy
   

   (You can use the arq-jbossas-remote profile for running tests as well)

3. This will deploy target/ticket-monster.war to the running instance of the server.

4. Now you can see the application running at http://localhost:8080/ticket-monster

1. Make sure that you have an OpenShift domain and you have created an application using the jbosseap-6 cartridge (for more details, get started here). If you want to use PostgreSQL, add the postgresql-9.2 cartridge too. Or, if you want to use MySQL, add the mysql-5.5 cartridge.
2. Ensure that the Git repository of the project is checked out.

1. Build TicketMonster using either:

   • the default profile (with H2 database support)

       mvn clean package	
     

   • the postgresql-openshift profile (with PostgreSQL support) if the PostgreSQL cartrdige is enabled in OpenShift.

       mvn clean package -Ppostgresql-openshift
     

   • the mysql-openshift profile (with MySQL support) if the MySQL cartrdige is enabled in OpenShift.

       mvn clean package -Pmysql-openshift
     

2. Copy the target/ticket-monster.warfile in the OpenShift Git repository(located at <root-of-openshift-application-git-repository>).

    cp target/ticket-monster.war <root-of-openshift-application-git-repository>/deployments/ROOT.war
   

3. Navigate to <root-of-openshift-application-git-repository> folder

4. Remove the existing src folder and pom.xml file.

    git rm -r src
    git rm pom.xml
   

5. Add the copied file to the repository, commit and push to Openshift

    git add deployments/ROOT.war
    git commit -m "Deploy TicketMonster"
    git push
   

6. Now you can see the application running at http://<app-name>-<domain-name>.rhcloud.com

NOTE: this version of TicketMonster uses the binary deployment style.