BAEL-150 Introduction to DeltaSpike
This commit is contained in:
Lukasz Rzeszotarski
File diff suppressed because it is too large
Load Diff
@@ -1,5 +0,0 @@
|
||||
<factorypath>
|
||||
<factorypathentry kind="PLUGIN" id="org.eclipse.jst.ws.annotations.core" enabled="true" runInBatchMode="false"/>
|
||||
<factorypathentry kind="VARJAR" id="M2_REPO/org/hibernate/hibernate-jpamodelgen/1.1.1.Final/hibernate-jpamodelgen-1.1.1.Final.jar" enabled="true" runInBatchMode="false"/>
|
||||
<factorypathentry kind="VARJAR" id="M2_REPO/org/hibernate/javax/persistence/hibernate-jpa-2.0-api/1.0.0.Final/hibernate-jpa-2.0-api-1.0.0.Final.jar" enabled="true" runInBatchMode="false"/>
|
||||
</factorypath>
|
||||
@@ -1,98 +0,0 @@
|
||||
baeldung-jee7-seed: Assortment of technologies including Arquillian
|
||||
========================
|
||||
Author: Pete Muir
|
||||
Level: Intermediate
|
||||
Technologies: CDI, JSF, JPA, EJB, JPA, JAX-RS, BV
|
||||
Summary: An example that incorporates multiple technologies
|
||||
Target Project: WildFly
|
||||
Source: <https://github.com/wildfly/quickstart/>
|
||||
|
||||
What is it?
|
||||
-----------
|
||||
|
||||
This is your project! It is a sample, deployable Maven 3 project to help you get your foot in the door developing with Java EE 7 on JBoss WildFly.
|
||||
|
||||
This project is setup to allow you to create a compliant Java EE 7 application using JSF 2.2, CDI 1.1, EJB 3.3, 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.
|
||||
|
||||
There is a tutorial for this quickstart in the [Getting Started Developing Applications Guide](https://github.com/wildfly/quickstart/guide/baeldung-jee7-seed/).
|
||||
|
||||
System requirements
|
||||
-------------------
|
||||
|
||||
All you need to build this project is Java 7.0 (Java SDK 1.7) or better, Maven 3.1 or better.
|
||||
|
||||
The application this project produces is designed to be run on JBoss WildFly.
|
||||
|
||||
|
||||
Configure Maven
|
||||
---------------
|
||||
|
||||
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md) before testing the quickstarts.
|
||||
|
||||
|
||||
Start JBoss WildFly with the Web Profile
|
||||
-------------------------
|
||||
|
||||
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
|
||||
|
||||
|
||||
Build and Deploy the Quickstart
|
||||
-------------------------
|
||||
|
||||
_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](https://github.com/jboss-developer/jboss-eap-quickstarts#build-and-deploy-the-quickstarts) for complete instructions and additional options._
|
||||
|
||||
1. Make sure you have started the JBoss Server 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/baeldung-jee7-seed.war` to the running instance of the server.
|
||||
|
||||
|
||||
Access the application
|
||||
---------------------
|
||||
|
||||
The application will be running at the following URL: <http://localhost:8080/baeldung-jee7-seed/>.
|
||||
|
||||
|
||||
Undeploy the Archive
|
||||
--------------------
|
||||
|
||||
1. Make sure you have started the JBoss Server 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
|
||||
|
||||
|
||||
Run the Arquillian Tests
|
||||
-------------------------
|
||||
|
||||
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](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md) for complete instructions and additional options._
|
||||
|
||||
1. Make sure you have started the JBoss Server as described above.
|
||||
2. Open a command line and navigate to the root directory of this quickstart.
|
||||
3. Type the following command to run the test goal with the following profile activated:
|
||||
|
||||
mvn clean test -Parq-wildfly-remote
|
||||
|
||||
|
||||
Run the Quickstart in JBoss Developer Studio or Eclipse
|
||||
-------------------------------------
|
||||
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](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/USE_JBDS.md)
|
||||
|
||||
|
||||
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
|
||||
Reference in New Issue
Block a user