kitchensink-html5-mobile quickstart is based on the
kitchensink quickstart and demonstrates a Java EE 6 mobile database application using HTML5, jQuery Mobile, JAX-RS, JPA 2.0, and REST in Red Hat JBoss Enterprise Application Platform.
What is a modern web application without mobile web support? This application also integrates jQuery mobile and basic client side device detection to give you both a desktop and mobile version of the interface. Both support the same features, including form validation, member registration, etc. However the mobile version adds in mobile layout, touch, and performance improvements needed to get you started with mobile web development on JBoss.
The application this project produces is designed to be run on Red Hat JBoss Enterprise Application Platform (JBoss 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.
An HTML5 compatible browser such as Chrome, Safari 5+, Firefox 5+, or IE 9+ are required. and note that some behaviors will vary slightly (ex. validations) based on browser support, especially IE 9.
Mobile web support is limited to Android and iOS devices. It should run on HP, and Black Berry devices as well. Windows Phone, and others will be supported as jQuery Mobile announces support.
With the prerequisites out of the way, you're ready to build and deploy.
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: Adding "-b 0.0.0.0" to the above commands will allow external clients (phones, tablets, desktops, etc…) connect through your local network.
For Linux: EAP_HOME/bin/standalone.sh -b 0.0.0.0 For Windows: EAP_HOME\bin\standalone.bat -b 0.0.0.0
Type this command to build and deploy the archive:
mvn clean jboss-as:deploy
target/jboss-kitchensink-html5-mobile.warto the running instance of the server.
Access the running client application in a browser at the following URL: http://localhost:8080/jboss-kitchensink-html5-mobile/.
When you are finished testing, type this command to undeploy the archive:
You can also start the server and deploy the quickstarts or run the Arquillian tests from Eclipse using JBoss tools. For more information, see Use JBoss Developer Studio or Eclipse to Run the Quickstarts
You can also deploy the application directly to OpenShift, Red Hat's cloud based PaaS offering, follow the instructions here
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 jboss-as:deploy -Pminify
#With Tests mvn clean jboss-as:deploy -Pminify,arq-jbossas-remote
By default, tests are configured to be skipped. The reason is that the sample test is an Arquillian test, which requires the use of a container. You can activate this test by selecting one of the container configuration provided for JBoss.
To run the test in JBoss, first start the container instance. Then, run the test goal with the following profile activated:
mvn clean test -Parq-jbossas-remote
Executing QUnit test cases is quite easy. Simply load the following HTML file in the browser you want to test.
You can also display the QUnit tests using the Eclipse built-in browser.
For more information on QUnit tests see http://docs.jquery.com/QUnit
If you created the project using the Maven archetype wizard in your IDE (Eclipse, NetBeans or IntelliJ IDEA), then there is nothing to do. You should already have an IDE project.
If you created the project from the command line using archetype:generate, then you need to import the project into your IDE. If you are using NetBeans 6.8 or IntelliJ IDEA 9, then all you have to do is open the project as an existing project. Both of these IDEs recognize Maven projects natively.
If you want to be able to debug into the source code or look at the Javadocs of any library in the project, you can run either of the following two commands to pull them into your local repository. The IDE should then detect them.
mvn dependency:sources mvn dependency:resolve -Dclassifier=javadoc