Author: Pete Muir
Level: Intermediate
Technologies: AngularJS, CDI, JPA, EJB, JPA, JAX-RS, BV
Summary: The kitchensink-angularjs
quickstart demonstrates a Java EE 7 application using AngularJS with JAX-RS, CDI, EJB, JPA, and Bean Validation.
Target Product: WildFly
Source: https://github.com/wildfly/quickstart/
The kitchensink-angularjs
quickstart is a deployable Maven 3 project to help you get your foot in the door developing with AngularJS on Java EE 7 with WildFly Application Server.
This project is setup to allow you to create a compliant Java EE 7 application using CDI 1.2, EJB 3.2, JPA 2.1 and Bean Validation 1.1. It includes a persistence unit and some sample persistence and transaction code to introduce you to database access in enterprise Java.
The application this project produces is designed to be run on WildFly Application Server 11 or later.
All you need to build this project is Java 8.0 (Java SDK 1.8) or later and Maven 3.3.1 or later. See Configure Maven for WildFly 11 to make sure you are configured correctly for testing the quickstarts.
For Linux: bin/standalone.sh
For Windows: bin\standalone.bat
mvn clean package wildfly:deploy
This will deploy target/kitchensink-angularjs.war
to the running instance of the server.
The application will be running at the following URL: http://localhost:8080/kitchensink-angularjs/.
mvn wildfly:undeploy
This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container.
mvn clean verify -Parq-remote
You can also let Arquillian manage the WildFly server by using the arq-managed
profile. For more information about how to run the Arquillian tests, see Run the Arquillian Tests.
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.
mvn clean package
Navigate to the functional-tests/
directory in this quickstart.
mvn clean verify -Parq-remote
If you prefer to run the functional tests using managed instance of the WildFly server, meaning the tests will start the server for you, type fhe following command:
mvn clean verify -Parq-managed
You can also start the server and deploy the quickstarts or run the Arquillian tests from Eclipse using JBoss tools. For general information about how to import a quickstart, add a WildFly server, and build and deploy a quickstart, see Use JBoss Developer Studio or Eclipse to Run the Quickstarts.
Note: If you have not installed the AngularJS Eclipse plugin into JBoss Developer Studio, you may see one or more of the following warnings when you import this project. You can ignore these warnings.
HTML Problem: Undefined attribute name (ng-app)
HTML Problem: Undefined attribute name (ng-click)
HTML Problem: Undefined attribute name (ng-disabled)
HTML Problem: Undefined attribute name (ng-hide)
HTML Problem: Undefined attribute name (ng-model)
HTML Problem: Undefined attribute name (ng-pattern)
HTML Problem: Undefined attribute name (ng-repeat)
HTML Problem: Undefined attribute name (ng-show)
HTML Problem: Undefined attribute name (ng-submit)
HTML Problem: Undefined attribute name (ng-view)
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