This is your project! It is a sample, deployable Maven 3 project to help you get your foot in the door developing with Backbone.js on Java EE 6 on Red Hat JBoss Enterprise Application Platform 6.1 or later.
kitchensink-backbone quickstart demonstrates how to use Backbone.js in a compliant Java EE 6 application using CDI 1.0, EJB 3.1, JPA 2.0 and Bean
Validation 1.0. It includes a persistence unit and some sample persistence and transaction code to introduce you to
database access in enterprise Java.
All of the code using the Backbone.js library can be found in /src/main/webapp/js/app.js. You will find the Model (and the Collection of the Model) there and the View where almost all the logic resides.
The application this project produces is designed to be run on Red Hat JBoss Enterprise Application Platform (EAP) 6.1 or later with the Red Hat JBoss Web Framework Kit (WFK) 2.7.
All you need to build this project is Java 6.0 (Java SDK 1.6) or later, Maven 3.0 or later.
If you have not yet done so, you must Configure Maven before testing the quickstarts.
The following shows the command line to start the server with the default profile:
For Linux: EAP_HOME/bin/standalone.sh For Windows: EAP_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.
Type this command to build and deploy the archive:
mvn clean package jboss-as:deploy
target/jboss-kitchensink-backbone.warto the running instance of the server.
The application will be running at the following URL: http://localhost:8080/jboss-kitchensink-backbone/.
When you are finished testing, type this command to undeploy the archive:
First, in the
Finally, wro4j runs in the compile phase so any standard build command like package, install, etc. will trigger it. The plugin is in a profile with an id of "minify" so you will want to specify that profile in your maven build.
NOTE: By default there are turn off tests so you must use the arquillian test profile to run tests when minifying. For example:
#No Tests mvn clean package jboss-as:deploy -Pminify,default
#With Tests mvn clean package jboss-as:deploy -Pminify,arq-jbossas-remote
This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container.
NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See Run the Arquillian Tests for complete instructions and additional options.
Type the following command to run the test goal with the following profile activated:
mvn clean test -Parq-jbossas-remote
This quickstart provides Arquillian functional tests as well. They are located in the functional-tests/ subdirectory under the root directory of this quickstart. Functional tests verify that your application behaves correctly from the user's point of view. The tests open a browser instance, simulate clicking around the page as a normal user would do, and then close the browser instance.
To run these tests, you must build the main project as described above.
Build the quickstart WAR using the following command:
mvn clean package
If you have a running instance of the JBoss EAP server, as described above, run the remote tests by typing the following command:
mvn clean verify -Parq-jbossas-remote
If you prefer to run the functional tests using managed instance of the JBoss EAP server, meaning the tests will start the server for you, type fhe following command:
mvn clean verify -Parq-jbossas-managed
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
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