Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Edits to README files to render metadata correctly and to use the correct term for JBoss EAP #119

Merged
merged 1 commit into from

2 participants

@sgilda
Owner

No description provided.

@rafabene
Owner

Good catches. It looks good!

@sgilda sgilda merged commit c82a87f into from
@sgilda sgilda deleted the branch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Feb 28, 2014
  1. @sgilda
This page is out of date. Refresh to see the latest.
Showing with 368 additions and 368 deletions.
  1. +21 −21 README.md
  2. +11 −11 cdi-add-interceptor-binding/README.md
  3. +7 −7 contacts-mobile-basic/README.md
  4. +15 −15 deltaspike-authorization/README.md
  5. +11 −11 deltaspike-beanbuilder/README.md
  6. +16 −16 deltaspike-beanmanagerprovider/README.md
  7. +11 −11 deltaspike-deactivatable/README.md
  8. +16 −16 deltaspike-exception-handling/README.md
  9. +22 −22 deltaspike-helloworld-jms/README.md
  10. +4 −4 deltaspike-partialbean-advanced/README.md
  11. +11 −11 deltaspike-partialbean-basic/README.md
  12. +16 −16 deltaspike-projectstage/README.md
  13. +15 −15 helloworld-errai/README.md
  14. +15 −15 helloworld-gwt/README.md
  15. +14 −14 helloworld-html5/README.md
  16. +16 −16 kitchensink-angularjs-bootstrap/README.md
  17. +16 −16 kitchensink-angularjs/README.md
  18. +15 −15 kitchensink-backbone/README.md
  19. +7 −7 kitchensink-cordova-contacts/README.md
  20. +7 −7 kitchensink-cordova/README.md
  21. +15 −15 kitchensink-deltaspike/README.md
  22. +11 −11 kitchensink-html5-mobile/README.md
  23. +11 −11 shrinkwrap-resolver/README.md
  24. +7 −7 spring-greeter/README.md
  25. +7 −7 spring-kitchensink-asyncrequestmapping/README.md
  26. +6 −6 spring-kitchensink-basic/README.md
  27. +6 −6 spring-kitchensink-controlleradvice/README.md
  28. +6 −6 spring-kitchensink-matrixvariables/README.md
  29. +6 −6 spring-kitchensink-springmvctest/README.md
  30. +7 −7 spring-petclinic/README.md
  31. +5 −5 spring-resteasy/README.md
  32. +15 −15 template/README.md
View
42 README.md
@@ -139,48 +139,48 @@ Run the Quickstarts
The root folder of each individual quickstart contains a README file with specific details on how to build and run the example. In most cases you do the following:
-* [Start the JBoss server](#start-the-jboss-server)
+* [Start the JBoss EAP server](#start-the-jboss-eap-server)
* [Build and deploy the quickstarts](#build-and-deploy-the-quickstarts)
-### Start the JBoss Server
+### Start the JBoss EAP Server
Before you deploy a quickstart, in most cases you need a running JBoss EAP server. A few of the Arquillian tests do not require a running server. This will be noted in the README for that quickstart.
-The JBoss server can be started a few different ways.
+The JBoss EAP server can be started a few different ways.
-* [Start the Default JBoss Server](#start-the-default-jboss-server): This is the default configuration. It defines minimal subsystems and services.
-* [Start the JBoss Server with the _full_ profile](#start-the-jboss-server-with-the-full-profile): This profile configures many of the commonly used subsystems and services.
-* [Start the JBoss Server with a custom configuration](#start-the-jboss-server-with-custom-configuration-options): Custom configuration parameters can be specified on the command line when starting the server.
+* [Start the Default JBoss EAP Server](#start-the-default-jboss-eap-server): This is the default configuration. It defines minimal subsystems and services.
+* [Start the JBoss EAP Server with the _full_ profile](#start-the-jboss-eap-server-with-the-full-profile): This profile configures many of the commonly used subsystems and services.
+* [Start the JBoss EAP Server with a custom configuration](#start-the-jboss-eap-server-with-custom-configuration-options): Custom configuration parameters can be specified on the command line when starting the server.
The README for each quickstart will specify which configuration is required to run the example.
-#### Start the Default JBoss Server
+#### Start the Default JBoss EAP Server
To start JBoss EAP:
-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 JBoss server:
+1. Open a command line and navigate to the root of the JBoss EAP directory.
+2. The following shows the command line to start the JBoss EAP server:
For Linux: JBOSS_HOME/bin/standalone.sh
For Windows: JBOSS_HOME\bin\standalone.bat
-#### Start the JBoss Server with the Full Profile
+#### Start the JBoss EAP Server with the Full Profile
To start JBoss EAP with the Full 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 JBoss server with the full profile:
+1. Open a command line and navigate to the root of the JBoss EAP directory.
+2. The following shows the command line to start the JBoss EAP server with the full profile:
For Linux: JBOSS_HOME/bin/standalone.sh -c standalone-full.xml
For Windows: JBOSS_HOME\bin\standalone.bat -c standalone-full.xml
-#### Start the JBoss Server with Custom Configuration Options
+#### Start the JBoss EAP Server with Custom Configuration Options
To start JBoss EAP with custom configuration options:
-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 JBoss server. Replace the CUSTOM_OPTIONS with the custom optional parameters specified in the quickstart.
+1. Open a command line and navigate to the root of the JBoss EAP directory.
+2. The following shows the command line to start the JBoss EAP server. Replace the CUSTOM_OPTIONS with the custom optional parameters specified in the quickstart.
For Linux: JBOSS_HOME/bin/standalone.sh CUSTOM_OPTIONS
For Windows: JBOSS_HOME\bin\standalone.bat CUSTOM_OPTIONS
@@ -200,7 +200,7 @@ In some cases, you may want to build the application to test for compile errors
#### Build and Deploy the Quickstart Archive
-1. Make sure you [start the JBoss server](#start-the-jboss-server) as described in the README.
+1. Make sure you [start the JBoss EAP server](#start-the-jboss-eap-server) as described in the README.
2. Open a command line and navigate to the root directory of the quickstart you want to run.
3. Use this command to build and deploy the archive:
@@ -219,7 +219,7 @@ You can verify the quickstarts build using one command. However, quickstarts tha
To build the quickstarts:
-1. Do not start the JBoss server.
+1. Do not start the JBoss EAP server.
2. Open a command line and navigate to the root directory of the quickstarts.
3. Use this command to build the quickstarts that do not have complex dependencies:
@@ -238,7 +238,7 @@ To undeploy the quickstarts from the root of the quickstart folder, you must pas
You can undeploy quickstarts using the following procedure:
-1. Start the JBoss server.
+1. Start the JBoss EAP server.
2. Open a command line and navigate to the root directory of the quickstarts.
3. Use this command to undeploy any deployed quickstarts:
@@ -256,8 +256,8 @@ You can either start the server yourself or let Arquillian manage its lifecycle
1. Test the quickstart on a remote server
- * Arquillian's remote container adapter expects a JBoss server instance to be already started prior to the test execution. You must [Start the JBoss server](#start-the-jboss-server) as described in the quickstart README file.
- * If you need to run the tests on a JBoss server running on a machine other than localhost, you can configure this, along with other options, in the `src/test/resources/arquillian.xml` file using the following properties:
+ * Arquillian's remote container adapter expects a JBoss EAP server instance to be already started prior to the test execution. You must [Start the JBoss EAP server](#start-the-jboss-eap-server) as described in the quickstart README file.
+ * If you need to run the tests on a JBoss EAP server running on a machine other than localhost, you can configure this, along with other options, in the `src/test/resources/arquillian.xml` file using the following properties:
<container qualifier="jboss" default="true">
<configuration>
@@ -272,7 +272,7 @@ You can either start the server yourself or let Arquillian manage its lifecycle
mvn clean test -Parq-jbossas-remote
2. Test the quickstart on a managed server
- Arquillian's managed container adapter requires that your server is not running as it will start the container for you. However, you must first let it know where to find the JBoss server directory. The simplest way to do this is to set the `JBOSS_HOME` environment variable to the full path to your JBoss server directory. Alternatively, you can set the path in the `jbossHome` property in the Arquillian configuration file.
+ Arquillian's managed container adapter requires that your server is not running as it will start the container for you. However, you must first let it know where to find the JBoss EAP directory. The simplest way to do this is to set the `JBOSS_HOME` environment variable to the full path to your JBoss EAP directory. Alternatively, you can set the path in the `jbossHome` property in the Arquillian configuration file.
* Open the `src/test/resources/arquillian.xml` file located in the quickstart directory.
* Find the configuration for the JBoss container. It should look like this:
View
22 cdi-add-interceptor-binding/README.md
@@ -1,12 +1,12 @@
cdi-add-interceptor-binding: An example of a Portable Extension and some of the APIs / SPIs of CDI
======================================================
-Author: Pete Muir
-Level: Intermediate
-Technologies: CDI, DeltaSpike
-Summary: Creating a basic CDI extension to automatically add an interceptor binding
-Target Product: WFK
-Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
-Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
+Author: Pete Muir
+Level: Intermediate
+Technologies: CDI, DeltaSpike
+Summary: Creating a basic CDI extension to automatically add an interceptor binding
+Target Product: WFK
+Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
+Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
What is it?
-----------
@@ -40,11 +40,11 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-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:
+1. Open a command line and navigate to the root of the JBoss EAP directory.
+2. The following shows the command line to start the server with the default profile:
For Linux: JBOSS_HOME/bin/standalone.sh
For Windows: JBOSS_HOME\bin\standalone.bat
@@ -57,7 +57,7 @@ This quickstart provides Arquillian tests. By default, these tests are configure
_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](../README.md#run-the-arquillian-tests) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
View
14 contacts-mobile-basic/README.md
@@ -65,10 +65,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-----------------------
-1. Open a command line and navigate to the root of the JBoss server directory.
+1. Open a command line and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server with the default profile:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -85,7 +85,7 @@ Start the JBoss Server
Build and Deploy the Quickstart
-------------------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -145,7 +145,7 @@ FAQ
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -165,13 +165,13 @@ To run these tests, you must build the main project as described above.
mvn clean package
3. Navigate to the functional-tests/ directory in this quickstart.
-4. If you have a running instance of the JBoss Server, as described above, run the remote tests by typing the following command:
+4. 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
-5. If you prefer to run the functional tests using managed instance of the JBoss server, meaning the tests will start the server for you, type the following command:
+5. 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 the following command:
-_NOTE: For this to work, Arquillian needs to know the location of the JBoss server. This can be declared through the `JBOSS_HOME` environment variable or the `jbossHome` property in `arquillian.xml`. See [Run the Arquillian Tests](../README.md#run-the-arquillian-tests) for complete instructions and additional options._
+_NOTE: For this to work, Arquillian needs to know the location of the JBoss EAP server. This can be declared through the `JBOSS_HOME` environment variable or the `jbossHome` property in `arquillian.xml`. See [Run the Arquillian Tests](../README.md#run-the-arquillian-tests) for complete instructions and additional options._
mvn clean verify -Parq-jbossas-managed
View
30 deltaspike-authorization/README.md
@@ -1,13 +1,13 @@
deltaspike-authorization: Demonstrate the creation of a custom authorization example using @SecurityBindingType from DeltaSpike
======================================================
-Author: Rafael Benevides
-Level: Beginner
-Technologies: JSF, CDI, Deltaspike
-Summary: Demonstrate the creation of a custom authorization example using @SecurityBindingType from DeltaSpike
-Prerequisites:
-Target Product: WFK
-Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
-Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
+Author: Rafael Benevides
+Level: Beginner
+Technologies: JSF, CDI, Deltaspike
+Summary: Demonstrate the creation of a custom authorization example using @SecurityBindingType from DeltaSpike
+Prerequisites:
+Target Product: WFK
+Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
+Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
What is it?
-----------
@@ -42,10 +42,10 @@ Add an Application User
This quickstart uses secured management interfaces and requires that you create an application user to access the running application. Instructions to set up the quickstart application user can be found here: [Add an Application User](../README.md#add-an-application-user)
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command line and navigate to the root of the JBoss server directory.
+1. Open a command line and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server with the default profile:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -56,7 +56,7 @@ 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](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -78,7 +78,7 @@ When you click on the `Admin Method` button you will be redirected to a error pa
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -97,13 +97,13 @@ To run these tests, you must build the main project as described above.
mvn clean package
3. Navigate to the functional-tests/ directory in this quickstart.
-4. If you have a running instance of the JBoss Server, as described above, run the remote tests by typing the following command:
+4. 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
-5. If you prefer to run the functional tests using managed instance of the JBoss server, meaning the tests will start the server for you, type the following command:
+5. 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 the following command:
-_NOTE: For this to work, Arquillian needs to know the location of the JBoss server. This can be declared through the `JBOSS_HOME` environment variable or the `jbossHome` property in `arquillian.xml`. See [Run the Arquillian Tests](../README.md#run-the-arquillian-tests) for complete instructions and additional options._
+_NOTE: For this to work, Arquillian needs to know the location of the JBoss EAP server. This can be declared through the `JBOSS_HOME` environment variable or the `jbossHome` property in `arquillian.xml`. See [Run the Arquillian Tests](../README.md#run-the-arquillian-tests) for complete instructions and additional options._
mvn clean verify -Parq-jbossas-managed
View
22 deltaspike-beanbuilder/README.md
@@ -1,12 +1,12 @@
deltaspike-beanbuilder: Shows how to create new beans using DeltaSpike utilities
======================================================
-Author: Rafael Benevides
-Level: Advanced
-Technologies: CDI, DeltaSpike
-Summary: Shows how to create new beans using DeltaSpike utilities.
-Target Product: WFK
-Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
-Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
+Author: Rafael Benevides
+Level: Advanced
+Technologies: CDI, DeltaSpike
+Summary: Shows how to create new beans using DeltaSpike utilities.
+Target Product: WFK
+Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
+Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
What is it?
-----------
@@ -32,11 +32,11 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-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:
+1. Open a command line and navigate to the root of the JBoss EAP directory.
+2. The following shows the command line to start the server with the default profile:
For Linux: JBOSS_HOME/bin/standalone.sh
For Windows: JBOSS_HOME\bin\standalone.bat
@@ -49,7 +49,7 @@ This quickstart provides Arquillian tests. By default, these tests are configure
_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](../README.md#run-the-arquillian-tests) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
View
32 deltaspike-beanmanagerprovider/README.md
@@ -1,13 +1,13 @@
deltaspike-beanmanagerprovider: Shows how to use DeltaSpike BeanManagerProvider to access CDI in a EntityListener
======================================================
-Author: Rafael Benevides
-Level: Intermediate
-Technologies: CDI, Deltaspike, JPA, JSF
-Summary: Shows how to use DeltaSpike BeanManagerProvider to access CDI in a EntityListener
-Prerequisites:
-Target Product: WFK
-Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
-Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
+Author: Rafael Benevides
+Level: Intermediate
+Technologies: CDI, Deltaspike, JPA, JSF
+Summary: Shows how to use DeltaSpike BeanManagerProvider to access CDI in a EntityListener
+Prerequisites:
+Target Product: WFK
+Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
+Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
What is it?
-----------
@@ -33,11 +33,11 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-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:
+1. Open a command line and navigate to the root of the JBoss EAP directory.
+2. The following shows the command line to start the server with the default profile:
For Linux: JBOSS_HOME/bin/standalone.sh
For Windows: JBOSS_HOME\bin\standalone.bat
@@ -48,7 +48,7 @@ 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](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -77,7 +77,7 @@ _NOTE: To fire the update audit, you must change one of the contact fields_
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -96,13 +96,13 @@ To run these tests, you must build the main project as described above.
mvn clean package
3. Navigate to the functional-tests/ directory in this quickstart.
-4. If you have a running instance of the JBoss Server, as described above, run the remote tests by typing the following command:
+4. 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
-5. If you prefer to run the functional tests using managed instance of the JBoss server, meaning the tests will start the server for you, type the following command:
+5. 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 the following command:
-_NOTE: For this to work, Arquillian needs to know the location of the JBoss server. This can be declared through the `JBOSS_HOME` environment variable or the `jbossHome` property in `arquillian.xml`. See [Run the Arquillian Tests](../README.md#run-the-arquillian-tests) for complete instructions and additional options._
+_NOTE: For this to work, Arquillian needs to know the location of the JBoss EAP server. This can be declared through the `JBOSS_HOME` environment variable or the `jbossHome` property in `arquillian.xml`. See [Run the Arquillian Tests](../README.md#run-the-arquillian-tests) for complete instructions and additional options._
mvn clean verify -Parq-jbossas-managed
View
22 deltaspike-deactivatable/README.md
@@ -1,12 +1,12 @@
deltaspike-deactivatable: Demonstrate usage of Deactivatable
======================================================
-Author: Rafael Benevides
-Level: Beginner
-Technologies: CDI, DeltaSpike
-Summary: Demonstrate usage of Deactivatable.
-Target Product: WFK
-Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
-Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
+Author: Rafael Benevides
+Level: Beginner
+Technologies: CDI, DeltaSpike
+Summary: Demonstrate usage of Deactivatable.
+Target Product: WFK
+Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
+Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
What is it?
-----------
@@ -29,11 +29,11 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-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:
+1. Open a command line and navigate to the root of the JBoss EAP directory.
+2. The following shows the command line to start the server with the default profile:
For Linux: JBOSS_HOME/bin/standalone.sh
For Windows: JBOSS_HOME\bin\standalone.bat
@@ -46,7 +46,7 @@ This quickstart provides Arquillian tests. By default, these tests are configure
_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](../README.md#run-the-arquillian-tests) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
View
32 deltaspike-exception-handling/README.md
@@ -1,13 +1,13 @@
deltaspike-exception-handling: An example how to use DeltaSpike exception handling
====================================================================================
-Author: Rafael Benevides
-Level: Intermediate
-Technologies: CDI, JSF, DeltaSpike
-Summary: Exception being handled by different handlers and purpose
-Prerequisites:
-Target Product: WFK
-Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
-Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
+Author: Rafael Benevides
+Level: Intermediate
+Technologies: CDI, JSF, DeltaSpike
+Summary: Exception being handled by different handlers and purpose
+Prerequisites:
+Target Product: WFK
+Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
+Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
What is it?
-----------
@@ -41,11 +41,11 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-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:
+1. Open a command line and navigate to the root of the JBoss EAP directory.
+2. The following shows the command line to start the server with the default profile:
For Linux: JBOSS_HOME/bin/standalone.sh
For Windows: JBOSS_HOME\bin\standalone.bat
@@ -56,7 +56,7 @@ 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](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -78,7 +78,7 @@ Click on `REST Invocation Test` link. The rest response is displayed on the ifra
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -97,13 +97,13 @@ To run these tests, you must build the main project as described above.
mvn clean package
3. Navigate to the functional-tests/ directory in this quickstart.
-4. If you have a running instance of the JBoss Server, as described above, run the remote tests by typing the following command:
+4. 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
-5. If you prefer to run the functional tests using managed instance of the JBoss server, meaning the tests will start the server for you, type the following command:
+5. 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 the following command:
-_NOTE: For this to work, Arquillian needs to know the location of the JBoss server. This can be declared through the `JBOSS_HOME` environment variable or the `jbossHome` property in `arquillian.xml`. See [Run the Arquillian Tests](../README.md#run-the-arquillian-tests) for complete instructions and additional options._
+_NOTE: For this to work, Arquillian needs to know the location of the JBoss EAP server. This can be declared through the `JBOSS_HOME` environment variable or the `jbossHome` property in `arquillian.xml`. See [Run the Arquillian Tests](../README.md#run-the-arquillian-tests) for complete instructions and additional options._
mvn clean verify -Parq-jbossas-managed
View
44 deltaspike-helloworld-jms/README.md
@@ -1,12 +1,12 @@
deltaspike-helloworld-jms: HelloWorld JMS Example Using DeltaSpike Configuration Properties
======================
-Author: Weston Price, Rafael Benevides
-Level: Intermediate
-Technologies: JMS, CDI, DeltaSpike
-Summary: Demonstrates a JMS client using DeltaSpike configuration properties
-Target Product: WFK
-Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
-Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
+Author: Weston Price, Rafael Benevides
+Level: Intermediate
+Technologies: JMS, CDI, DeltaSpike
+Summary: Demonstrates a JMS client using DeltaSpike configuration properties
+Target Product: WFK
+Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
+Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
What is it?
-----------
@@ -38,7 +38,7 @@ Add an Application User
This quickstart uses secured management interfaces and requires that you create an application user to access the running application. Instructions to set up the quickstart application user can be found here: [Add an Application User](../README.md#add-an-application-user)
-Configure the JBoss Server
+Configure the JBoss EAP Server
---------------------------
You must first add the JMS `test` queue to the application server configuration file. You can configure JMS by running the `configure-jms.cli` script provided in the root directory of this quickstart, by using the JBoss CLI interactively, or by manually editing the configuration file.
@@ -51,7 +51,7 @@ _NOTE - Before you begin:_
#### Configure JMS by Running the JBoss CLI Script
-1. Start the JBoss server by typing the following:
+1. Start the JBoss EAP server by typing the following:
For Linux: JBOSS_HOME_SERVER_1/bin/standalone.sh -c standalone-full.xml
For Windows: JBOSS_HOME_SERVER_1\bin\standalone.bat -c standalone-full.xml
@@ -67,7 +67,7 @@ This script adds the `test` queue to the `messaging` subsystem in the server con
#### Configure JMS Using the JBoss CLI Tool Interactively
-1. Start the JBoss server by typing the following:
+1. Start the JBoss EAP server by typing the following:
For Linux: JBOSS_HOME_SERVER_1/bin/standalone.sh -c standalone-full.xml
For Windows: JBOSS_HOME_SERVER_1\bin\standalone.bat -c standalone-full.xml
@@ -82,7 +82,7 @@ This script adds the `test` queue to the `messaging` subsystem in the server con
#### Configure JMS by Manually Editing the Server Configuration File
-1. If it is running, stop the JBoss server.
+1. If it is running, stop the JBoss EAP server.
2. Backup the file: `JBOSS_HOME/standalone/configuration/standalone-full.xml`
3. Open the file: JBOSS_HOME/standalone/configuration/standalone-full.xml
4. Add the JMS `test` queue as follows:
@@ -97,13 +97,13 @@ This script adds the `test` queue to the `messaging` subsystem in the server con
<entry name="java:jboss/exported/jms/queue/test"/>
</jms-queue>
</jms-destinations>
- * Save the changes and close the file.
+ * Save the changes and close the file.
-Start the JBoss Server with the Full Profile
+Start the JBoss EAP Server with the Full Profile
---------------------------------------------------------------------------------
-1. Open a command line and navigate to the root of the JBoss server directory.
+1. Open a command line and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server with the full profile:
For Linux: JBOSS_HOME/bin/standalone.sh -c standalone-full.xml
@@ -115,7 +115,7 @@ 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](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -156,7 +156,7 @@ The configuration is injected by using the `@ConfigProperty` annotation
@ConfigProperty(name = "username", defaultValue = "quickstartUser")
private String usernameConfig;
-The following properties can be configured:
+The following properties can be configured:
* `username`
@@ -205,7 +205,7 @@ You can overwrite these properties by adding the value that you want on file `sr
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -219,7 +219,7 @@ You can remove the JMS configuration by running the `remove-jms.cli` script pro
#### Remove the JMS Configuration by Running the JBoss CLI Script
-1. Start the JBoss server by typing the following:
+1. Start the JBoss EAP server by typing the following:
For Linux: JBOSS_HOME_SERVER_1/bin/standalone.sh -c standalone-full.xml
For Windows: JBOSS_HOME_SERVER_1\bin\standalone.bat -c standalone-full.xml
@@ -234,7 +234,7 @@ This script removes the `test` queue from the `messaging` subsystem in the serve
#### Remove the JMS Configuration Manually
-1. If it is running, stop the JBoss server.
+1. If it is running, stop the JBoss EAP server.
2. Replace the `JBOSS_HOME/standalone/configuration/standalone-full.xml` file with the back-up copy of the file.
Run the Arquillian Functional Tests
@@ -250,13 +250,13 @@ To run these tests, you must build the main project as described above.
mvn clean package
3. Navigate to the functional-tests/ directory in this quickstart.
-4. If you have a running instance of the JBoss Server, as described above, run the remote tests by typing the following command:
+4. 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
-5. If you prefer to run the functional tests using managed instance of the JBoss server, meaning the tests will start the server for you, type the following command:
+5. 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 the following command:
-_NOTE: For this to work, Arquillian needs to know the location of the JBoss server. This can be declared through the `JBOSS_HOME` environment variable or the `jbossHome` property in `arquillian.xml`. See [Run the Arquillian Tests](../README.md#run-the-arquillian-tests) for complete instructions and additional options._
+_NOTE: For this to work, Arquillian needs to know the location of the JBoss EAP server. This can be declared through the `JBOSS_HOME` environment variable or the `jbossHome` property in `arquillian.xml`. See [Run the Arquillian Tests](../README.md#run-the-arquillian-tests) for complete instructions and additional options._
mvn clean verify -Parq-jbossas-managed
View
8 deltaspike-partialbean-advanced/README.md
@@ -30,11 +30,11 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-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:
+1. Open a command line and navigate to the root of the JBoss EAP directory.
+2. The following shows the command line to start the server with the default profile:
For Linux: JBOSS_HOME/bin/standalone.sh
For Windows: JBOSS_HOME\bin\standalone.bat
@@ -47,7 +47,7 @@ This quickstart provides Arquillian tests. By default, these tests are configure
_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](../README.md#arquilliantests) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
View
22 deltaspike-partialbean-basic/README.md
@@ -1,12 +1,12 @@
deltaspike-partialbean-basic: HelloWorld Example of the DeltaSpike PartialBean API
======================================================
-Author: Jess Sightler
-Level: Advanced
-Technologies: CDI, DeltaSpike
-Summary: Demonstrates a class providing a dynamic implementation of a DeltaSpike Partial Bean
-Target Product: WFK
-Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
-Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
+Author: Jess Sightler
+Level: Advanced
+Technologies: CDI, DeltaSpike
+Summary: Demonstrates a class providing a dynamic implementation of a DeltaSpike Partial Bean
+Target Product: WFK
+Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
+Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
What is it?
-----------
@@ -34,11 +34,11 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-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:
+1. Open a command line and navigate to the root of the JBoss EAP directory.
+2. The following shows the command line to start the server with the default profile:
For Linux: JBOSS_HOME/bin/standalone.sh
For Windows: JBOSS_HOME\bin\standalone.bat
@@ -51,7 +51,7 @@ This quickstart provides Arquillian tests. By default, these tests are configure
_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](../README.md#arquilliantests) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
View
32 deltaspike-projectstage/README.md
@@ -1,13 +1,13 @@
deltaspike-projectstage: Demonstrate usage of DeltaSpike project stage and shows usage of a conditional @Exclude
======================================================
-Author: Rafael Benevides
-Level: Beginner
-Technologies: JSF, CDI, Deltaspike
-Summary: Demonstrate usage of DeltaSpike project stage and shows usage of a conditional @Exclude
-Prerequisites:
-Target Product: WFK
-Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
-Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
+Author: Rafael Benevides
+Level: Beginner
+Technologies: JSF, CDI, Deltaspike
+Summary: Demonstrate usage of DeltaSpike project stage and shows usage of a conditional @Exclude
+Prerequisites:
+Target Product: WFK
+Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
+Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
What is it?
-----------
@@ -47,11 +47,11 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-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:
+1. Open a command line and navigate to the root of the JBoss EAP directory.
+2. The following shows the command line to start the server with the default profile:
For Linux: JBOSS_HOME/bin/standalone.sh
For Windows: JBOSS_HOME\bin\standalone.bat
@@ -61,7 +61,7 @@ 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](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -86,7 +86,7 @@ Look at *List of available CDI instances for MyBean* table and realize that the
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -105,13 +105,13 @@ To run these tests, you must build the main project as described above.
mvn clean package
3. Navigate to the functional-tests/ directory in this quickstart.
-4. If you have a running instance of the JBoss Server, as described above, run the remote tests by typing the following command:
+4. 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
-5. If you prefer to run the functional tests using managed instance of the JBoss server, meaning the tests will start the server for you, type the following command:
+5. 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 the following command:
-_NOTE: For this to work, Arquillian needs to know the location of the JBoss server. This can be declared through the `JBOSS_HOME` environment variable or the `jbossHome` property in `arquillian.xml`. See [Run the Arquillian Tests](../README.md#run-the-arquillian-tests) for complete instructions and additional options._
+_NOTE: For this to work, Arquillian needs to know the location of the JBoss EAP server. This can be declared through the `JBOSS_HOME` environment variable or the `jbossHome` property in `arquillian.xml`. See [Run the Arquillian Tests](../README.md#run-the-arquillian-tests) for complete instructions and additional options._
mvn clean verify -Parq-jbossas-managed
View
30 helloworld-errai/README.md
@@ -1,12 +1,12 @@
helloworld-errai: Hello World Using the Errai Framework
=======================================================
-Author: Jonathon Fuerth
-Level: Beginner
-Technologies: Errai, JAX-RS, GWT
-Summary: Helloworld using the Errai framework
-Target Product: WFK
-Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
-Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
+Author: Jonathon Fuerth
+Level: Beginner
+Technologies: Errai, JAX-RS, GWT
+Summary: Helloworld using the Errai framework
+Target Product: WFK
+Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
+Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
What is it?
-----------
@@ -31,11 +31,11 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-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:
+1. Open a command line and navigate to the root of the JBoss EAP directory.
+2. The following shows the command line to start the server with the default profile:
For Linux: JBOSS_HOME/bin/standalone.sh
For Windows: JBOSS_HOME\bin\standalone.bat
@@ -46,7 +46,7 @@ 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](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -64,7 +64,7 @@ The application will be running at the following URL: <http://localhost:8080/jb
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -76,7 +76,7 @@ Run the Application in GWT Dev Mode
GWT Dev Mode provides an edit-save-refresh development experience. If you plan to modify this demo, we recommend you start the application in Dev Mode so you don't have to repackage the entire application every time you change it.
-1. Deploy the WAR file and start the JBoss Server as described above.
+1. Deploy the WAR file and start the JBoss EAP server as described above.
2. Open a command line and navigate to the helloworld-errai quickstart directory
3. Execute the following command:
@@ -96,11 +96,11 @@ To run these tests, you must build the main project as described above.
mvn clean package
3. Navigate to the functional-tests/ directory in this quickstart.
-4. If you have a running instance of the JBoss Server, as described above, run the remote tests by typing the following command:
+4. 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
-5. If you prefer to run the functional tests using managed instance of the JBoss server, meaning the tests will start the server for you, type fhe following command:
+5. 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
View
30 helloworld-gwt/README.md
@@ -1,12 +1,12 @@
helloworld-gwt: Helloworld with a GWT (Google Web Toolkit) Front End Client
===========================================================================
-Author: Christian Sadilek
-Level: Beginner
-Technologies: GWT
-Summary: Demonstrates the use of CDI 1.0 and JAX-RS with a GWT front-end client
-Target Product: WFK
-Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
-Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
+Author: Christian Sadilek
+Level: Beginner
+Technologies: GWT
+Summary: Demonstrates the use of CDI 1.0 and JAX-RS with a GWT front-end client
+Target Product: WFK
+Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
+Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
What is it?
-----------
@@ -30,11 +30,11 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-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:
+1. Open a command line and navigate to the root of the JBoss EAP directory.
+2. The following shows the command line to start the server with the default profile:
For Linux: JBOSS_HOME/bin/standalone.sh
For Windows: JBOSS_HOME\bin\standalone.bat
@@ -45,7 +45,7 @@ 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](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -63,7 +63,7 @@ The application will be running at the following URL: <http://localhost:8080/jb
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -75,7 +75,7 @@ Run the Application in GWT Dev Mode
GWT Dev Mode provides an edit-save-refresh development experience. If you plan to modify this demo, we recommend you start the application in Dev Mode so you don't have to repackage the entire application every time you change it.
-1. Deploy the WAR file and start the JBoss Server as described above.
+1. Deploy the WAR file and start the JBoss EAP server as described above.
2. Open a command line and navigate to the helloworld-errai quickstart directory
3. Execute the following command:
@@ -95,11 +95,11 @@ To run these tests, you must build the main project as described above.
mvn clean package
3. Navigate to the functional-tests/ directory in this quickstart.
-4. If you have a running instance of the JBoss Server, as described above, run the remote tests by typing the following command:
+4. 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
-5. If you prefer to run the functional tests using managed instance of the JBoss server, meaning the tests will start the server for you, type fhe following command:
+5. 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
View
28 helloworld-html5/README.md
@@ -1,12 +1,12 @@
helloworld-html5: HTML5 + REST Hello World Example
===================
-Author: Jay Balunas, Burr Sutter, Douglas Campos, Bruno Olivera
-Level: Beginner
-Technologies: CDI, JAX-RS, HTML5
-Summary: Basic HTML5 |Demonstrates the use of CDI 1.0 and JAX-RS using the HTML5 architecture and RESTful services on the backend
-Target Product: WFK
-Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
-Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
+Author: Jay Balunas, Burr Sutter, Douglas Campos, Bruno Olivera
+Level: Beginner
+Technologies: CDI, JAX-RS, HTML5
+Summary: Basic HTML5 |Demonstrates the use of CDI 1.0 and JAX-RS using the HTML5 architecture and RESTful services on the backend
+Target Product: WFK
+Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
+Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
What is it?
-----------
@@ -38,11 +38,11 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-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:
+1. Open a command line and navigate to the root of the JBoss EAP directory.
+2. The following shows the command line to start the server with the default profile:
For Linux: JBOSS_HOME/bin/standalone.sh
For Windows: JBOSS_HOME\bin\standalone.bat
@@ -53,7 +53,7 @@ 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](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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 both the client and service applications:
@@ -76,7 +76,7 @@ You can also test the REST endpoint as follows. Feel free to replace `YOUR_NAME`
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -96,11 +96,11 @@ To run these tests, you must build the main project as described above.
mvn clean package
3. Navigate to the functional-tests/ directory in this quickstart.
-4. If you have a running instance of the JBoss Server, as described above, run the remote tests by typing the following command:
+4. 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
-5. If you prefer to run the functional tests using managed instance of the JBoss server, meaning the tests will start the server for you, type fhe following command:
+5. 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
View
32 kitchensink-angularjs-bootstrap/README.md
@@ -1,12 +1,12 @@
kitchensink-angularjs-bootstrap: Shows how to use AngularJS and Twitter Bootstrap with JAX-RS and Java EE on JBoss
========================
-Author: Vineet Reynolds
-Level: Intermediate
-Technologies: AngularJS, CDI, JPA, EJB, JPA, JAX-RS, BV
-Summary: An example that incorporates multiple technologies
-Target Product: WFK
-Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
-Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts>
+Author: Vineet Reynolds
+Level: Intermediate
+Technologies: AngularJS, CDI, JPA, EJB, JPA, JAX-RS, BV
+Summary: An example that incorporates multiple technologies
+Target Product: WFK
+Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
+Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts>
What is it?
-----------
@@ -29,11 +29,11 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-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:
+1. Open a command line and navigate to the root of the JBoss EAP directory.
+2. The following shows the command line to start the server with the default profile:
For Linux: JBOSS_HOME/bin/standalone.sh
For Windows: JBOSS_HOME\bin\standalone.bat
@@ -44,7 +44,7 @@ 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](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -62,7 +62,7 @@ The application will be running at the following URL: <http://localhost:8080/jbo
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -76,7 +76,7 @@ This quickstart provides Arquillian tests. By default, these tests are configure
_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](../README.md#run-the-arquillian-tests) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -96,11 +96,11 @@ To run these tests, you must build the main project as described above.
mvn clean package
3. Navigate to the functional-tests/ directory in this quickstart.
-4. If you have a running instance of the JBoss Server, as described above, run the remote tests by typing the following command:
+4. 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
-5. If you prefer to run the functional tests using managed instance of the JBoss server, meaning the tests will start the server for you, type fhe following command:
+5. 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
@@ -166,7 +166,7 @@ You can now deploy the changes to your OpenShift application using git as follow
git commit -m "kitchensink-angularjs-bootstrap quickstart on OpenShift"
git push
-OpenShift will build the application using Maven, and deploy it to the JBoss server. If successful, you should see output similar to:
+OpenShift will build the application using Maven, and deploy it to the JBoss EAP server. If successful, you should see output similar to:
remote: [INFO] ------------------------------------------------------------------------
remote: [INFO] BUILD SUCCESS
View
32 kitchensink-angularjs/README.md
@@ -1,12 +1,12 @@
kitchensink-angularjs: Shows how to use AngularJS with JAX-RS and Java EE on JBoss
========================
-Author: Pete Muir
-Level: Intermediate
-Technologies: AngularJS, CDI, JPA, EJB, JPA, JAX-RS, BV
-Summary: An example that incorporates multiple technologies
-Target Product: WFK
-Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
-Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts>
+Author: Pete Muir
+Level: Intermediate
+Technologies: AngularJS, CDI, JPA, EJB, JPA, JAX-RS, BV
+Summary: An example that incorporates multiple technologies
+Target Product: WFK
+Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
+Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts>
What is it?
-----------
@@ -29,11 +29,11 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-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:
+1. Open a command line and navigate to the root of the JBoss EAP directory.
+2. The following shows the command line to start the server with the default profile:
For Linux: JBOSS_HOME/bin/standalone.sh
For Windows: JBOSS_HOME\bin\standalone.bat
@@ -44,7 +44,7 @@ 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](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -62,7 +62,7 @@ The application will be running at the following URL: <http://localhost:8080/jbo
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -76,7 +76,7 @@ This quickstart provides Arquillian tests. By default, these tests are configure
_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](../README.md#run-the-arquillian-tests) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -96,11 +96,11 @@ To run these tests, you must build the main project as described above.
mvn clean package
3. Navigate to the functional-tests/ directory in this quickstart.
-4. If you have a running instance of the JBoss Server, as described above, run the remote tests by typing the following command:
+4. 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
-5. If you prefer to run the functional tests using managed instance of the JBoss server, meaning the tests will start the server for you, type fhe following command:
+5. 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
@@ -166,7 +166,7 @@ You can now deploy the changes to your OpenShift application using git as follow
git commit -m "kitchensink-angularjs quickstart on OpenShift"
git push
-OpenShift will build the application using Maven, and deploy it to the JBoss server. If successful, you should see output similar to:
+OpenShift will build the application using Maven, and deploy it to the JBoss EAP server. If successful, you should see output similar to:
remote: [INFO] ------------------------------------------------------------------------
remote: [INFO] BUILD SUCCESS
View
30 kitchensink-backbone/README.md
@@ -1,12 +1,12 @@
kitchensink-backbone: Shows how to use Backbone.js with JAX-RS and Java EE on JBoss
========================
-Author: Joshua Wilson
-Level: Intermediate
-Technologies: Backbone, CDI, JPA, EJB, JPA, JAX-RS, BV
-Summary: An example of Backbone.js integrated with jQuery, REST, and a Java back-end running on JBoss.
-Target Product: WFK
-Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
-Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
+Author: Joshua Wilson
+Level: Intermediate
+Technologies: Backbone, CDI, JPA, EJB, JPA, JAX-RS, BV
+Summary: An example of Backbone.js integrated with jQuery, REST, and a Java back-end running on JBoss.
+Target Product: WFK
+Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
+Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
What is it?
-----------
@@ -38,11 +38,11 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-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:
+1. Open a command line and navigate to the root of the JBoss EAP directory.
+2. The following shows the command line to start the server with the default profile:
For Linux: JBOSS_HOME/bin/standalone.sh
For Windows: JBOSS_HOME\bin\standalone.bat
@@ -55,7 +55,7 @@ _NOTE: The following build command assumes you have configured your Maven user s
Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for
complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -73,7 +73,7 @@ The application will be running at the following URL: <http://localhost:8080/jbo
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -90,7 +90,7 @@ _NOTE: The following commands assume you have configured your Maven user setting
Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#run-the-arquillian-tests) for complete
instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -110,11 +110,11 @@ To run these tests, you must build the main project as described above.
mvn clean package
3. Navigate to the functional-tests/ directory in this quickstart.
-4. If you have a running instance of the JBoss Server, as described above, run the remote tests by typing the following command:
+4. 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
-5. If you prefer to run the functional tests using managed instance of the JBoss server, meaning the tests will start the server for you, type fhe following command:
+5. 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
View
14 kitchensink-cordova-contacts/README.md
@@ -1,12 +1,12 @@
kitchensink-cordova-contacts: Example Mobile Applications Using Hybrid HTML5 + REST with Apache Cordova
===============================================================================================
-Author: Vineet Reynolds
-Level: Intermediate
-Technologies: HTML5, REST, Apache Cordova
-Summary: Based on kitchensink, but uses hybrid HTML5 running as a native application on mobiles
-Target Product: WFK
-Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
-Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
+Author: Vineet Reynolds
+Level: Intermediate
+Technologies: HTML5, REST, Apache Cordova
+Summary: Based on kitchensink, but uses hybrid HTML5 running as a native application on mobiles
+Target Product: WFK
+Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
+Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
What is it?
-----------
View
14 kitchensink-cordova/README.md
@@ -1,12 +1,12 @@
kitchensink-cordova: Example Mobile Applications Using Hybrid HTML5 + REST with Apache Cordova
===============================================================================================
-Author: Kris Borchers
-Level: Intermediate
-Technologies: HTML5, REST, Apache Cordova
-Summary: Based on kitchensink, but uses hybrid HTML5 running as a native application on mobiles
-Target Product: WFK
-Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
-Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
+Author: Kris Borchers
+Level: Intermediate
+Technologies: HTML5, REST, Apache Cordova
+Summary: Based on kitchensink, but uses hybrid HTML5 running as a native application on mobiles
+Target Product: WFK
+Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
+Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
What is it?
-----------
View
30 kitchensink-deltaspike/README.md
@@ -1,12 +1,12 @@
kitchensink-deltaspike: Assortment of technologies including Arquillian and DeltaSpike CDI extensions
========================
-Author: Pete Muir, Bernard Tison
-Level: Intermediate
-Technologies: CDI, JSF, JPA, JPA, JAX-RS, BV, DeltaSpike
-Summary: A version of kitchensink that uses DeltaSpike @Transactional
-Target Product: WFK
-Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
-Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
+Author: Pete Muir, Bernard Tison
+Level: Intermediate
+Technologies: CDI, JSF, JPA, JPA, JAX-RS, BV, DeltaSpike
+Summary: A version of kitchensink that uses DeltaSpike @Transactional
+Target Product: WFK
+Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
+Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
What is it?
-----------
@@ -45,11 +45,11 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-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:
+1. Open a command line and navigate to the root of the JBoss EAP directory.
+2. The following shows the command line to start the server with the default profile:
For Linux: JBOSS_HOME/bin/standalone.sh
For Windows: JBOSS_HOME\bin\standalone.bat
@@ -60,7 +60,7 @@ 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](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -78,7 +78,7 @@ The application will be running at the following URL: <http://localhost:8080/jbo
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -92,7 +92,7 @@ This quickstart provides Arquillian tests. By default, these tests are configure
_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](../README.md#run-the-arquillian-tests) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -116,11 +116,11 @@ To run these tests, you must build the main project as described above.
mvn clean package
3. Navigate to the functional-tests/ directory in this quickstart.
-4. If you have a running instance of the JBoss Server, as described above, run the remote tests by typing the following command:
+4. 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
-5. If you prefer to run the functional tests using managed instance of the JBoss server, meaning the tests will start the server for you, type fhe following command:
+5. 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
View
22 kitchensink-html5-mobile/README.md
@@ -1,12 +1,12 @@
kitchensink-html5-mobile: Example Application Using Multiple HTML5, Mobile & JAX-RS Technologies
=========================================================================================================
-Author: Jay Balunas
-Level: Beginner
-Technologies: CDI, HTML5, REST
-Summary: Based on kitchensink, but uses HTML5, making it suitable for mobile and tablet computers
-Target Product: WFK
-Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
-Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts>
+Author: Jay Balunas
+Level: Beginner
+Technologies: CDI, HTML5, REST
+Summary: Based on kitchensink, but uses HTML5, making it suitable for mobile and tablet computers
+Target Product: WFK
+Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
+Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts>
What is it?
-----------
@@ -37,10 +37,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-----------------------
-1. Open a command line and navigate to the root of the JBoss server directory.
+1. Open a command line and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server with the default profile:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -57,7 +57,7 @@ Start the JBoss Server
Build and Deploy the Quickstart
-------------------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -75,7 +75,7 @@ Access the running client application in a browser at the following URL: <http:/
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
View
22 shrinkwrap-resolver/README.md
@@ -1,12 +1,12 @@
shrinkwrap-resolver: Demonstrate usage of Shrinkwrap resolver
==============================================================
-Author: Rafael Benevides
-Level: Intermediate
-Technologies: CDI, Arquillian, Shrinkwrap
-Summary: Demonstrate usage of some Shrinkwrap resolver use cases
-Target Product: WFK
-Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
-Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
+Author: Rafael Benevides
+Level: Intermediate
+Technologies: CDI, Arquillian, Shrinkwrap
+Summary: Demonstrate usage of some Shrinkwrap resolver use cases
+Target Product: WFK
+Product Versions: EAP 6.1, EAP 6.2, WFK 2.5
+Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
What is it?
@@ -49,11 +49,11 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-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:
+1. Open a command line and navigate to the root of the JBoss EAP directory.
+2. The following shows the command line to start the server with the default profile:
For Linux: JBOSS_HOME/bin/standalone.sh
For Windows: JBOSS_HOME\bin\standalone.bat
@@ -65,7 +65,7 @@ This quickstart provides Arquillian tests. By default, these tests are configure
_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](../README.md#run-the-arquillian-tests) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
View
14 spring-greeter/README.md
@@ -51,11 +51,11 @@ Configure Maven
If you have not yet done so, you must Configure Maven before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
---------------
-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:
+1. Open a command line and navigate to the root of the JBoss EAP directory.
+2. The following shows the command line to start the server with the default profile:
For Linux: JBOSS_HOME/bin/standalone.sh
For Windows: JBOSS_HOME\bin\standalone.bat
@@ -67,7 +67,7 @@ _NOTE: The following build command assumes you have configured your Maven user s
Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts)
for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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 jboss-as:deploy
@@ -84,7 +84,7 @@ The application will be running at the following URL: <http://localhost:8080/jbo
Undeploy the Archive
---------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -107,11 +107,11 @@ To run these tests, you must build the main project as described above.
mvn clean package
3. Navigate to the functional-tests/ directory in this quickstart.
-4. If you have a running instance of the JBoss Server, as described above, run the remote tests by typing the following command:
+4. 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
-5. If you prefer to run the functional tests using managed instance of the JBoss server, meaning the tests will start the
+5. 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 the following command:
mvn clean verify -Parq-jbossas-managed
View
14 spring-kitchensink-asyncrequestmapping/README.md
@@ -59,11 +59,11 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-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:
+1. Open a command line and navigate to the root of the JBoss EAP directory.
+2. The following shows the command line to start the server with the default profile:
For Linux: JBOSS_HOME/bin/standalone.sh
For Windows: JBOSS_HOME\bin\standalone.bat
@@ -76,7 +76,7 @@ _NOTE: The following build command assumes you have configured your Maven user s
Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts)
for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -94,7 +94,7 @@ The application will be running at the following URL: <http://localhost:8080/jbo
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -116,11 +116,11 @@ To run these tests, you must build the main project as described above.
mvn clean package
3. Navigate to the functional-tests/ directory in this quickstart.
-4. If you have a running instance of the JBoss Server, as described above, run the remote tests by typing the following command:
+4. 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
-5. If you prefer to run the functional tests using managed instance of the JBoss server, meaning the tests will start the
+5. 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 the following command:
mvn clean verify -Parq-jbossas-managed
View
12 spring-kitchensink-basic/README.md
@@ -56,10 +56,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command line and navigate to the root of the JBoss server directory.
+1. Open a command line and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -73,7 +73,7 @@ _NOTE: The following build command assumes you have configured your Maven user s
Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts)
for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -91,7 +91,7 @@ The application will be running at the following URL: <http://localhost:8080/jbo
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -113,11 +113,11 @@ To run these tests, you must build the main project as described above.
mvn clean package
3. Navigate to the functional-tests/ directory in this quickstart.
-4. If you have a running instance of the JBoss Server, as described above, run the remote tests by typing the following command:
+4. 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
-5. If you prefer to run the functional tests using managed instance of the JBoss server, meaning the tests will start the
+5. 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 the following command:
mvn clean verify -Parq-jbossas-managed
View
12 spring-kitchensink-controlleradvice/README.md
@@ -60,10 +60,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command line and navigate to the root of the JBoss server directory.
+1. Open a command line and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -77,7 +77,7 @@ _NOTE: The following build command assumes you have configured your Maven user s
Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts)
for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -95,7 +95,7 @@ The application will be running at the following URL: <http://localhost:8080/jbo
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -117,11 +117,11 @@ To run these tests, you must build the main project as described above.
mvn clean package
3. Navigate to the functional-tests/ directory in this quickstart.
-4. If you have a running instance of the JBoss Server, as described above, run the remote tests by typing the following command:
+4. 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
-5. If you prefer to run the functional tests using managed instance of the JBoss server, meaning the tests will start the
+5. 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 the following command:
mvn clean verify -Parq-jbossas-managed
View
12 spring-kitchensink-matrixvariables/README.md
@@ -66,10 +66,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command line and navigate to the root of the JBoss server directory.
+1. Open a command line and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -83,7 +83,7 @@ _NOTE: The following build command assumes you have configured your Maven user s
Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts)
for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -101,7 +101,7 @@ The application will be running at the following URL: <http://localhost:8080/jbo
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -123,11 +123,11 @@ To run these tests, you must build the main project as described above.
mvn clean package
3. Navigate to the functional-tests/ directory in this quickstart.
-4. If you have a running instance of the JBoss Server, as described above, run the remote tests by typing the following command:
+4. 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
-5. If you prefer to run the functional tests using managed instance of the JBoss server, meaning the tests will start the
+5. 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 the following command:
mvn clean verify -Parq-jbossas-managed
View
12 spring-kitchensink-springmvctest/README.md
@@ -60,10 +60,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command line and navigate to the root of the JBoss server directory.
+1. Open a command line and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -77,7 +77,7 @@ _NOTE: The following build command assumes you have configured your Maven user s
Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts)
for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -95,7 +95,7 @@ The application will be running at the following URL: <http://localhost:8080/jbo
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -117,11 +117,11 @@ To run these tests, you must build the main project as described above.
mvn clean package
3. Navigate to the functional-tests/ directory in this quickstart.
-4. If you have a running instance of the JBoss Server, as described above, run the remote tests by typing the following command:
+4. 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
-5. If you prefer to run the functional tests using managed instance of the JBoss server, meaning the tests will start the
+5. 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 the following command:
mvn clean verify -Parq-jbossas-managed
View
14 spring-petclinic/README.md
@@ -54,11 +54,11 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-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:
+1. Open a command line and navigate to the root of the JBoss EAP directory.
+2. The following shows the command line to start the server with the default profile:
For Linux: JBOSS_HOME/bin/standalone.sh
For Windows: JBOSS_HOME\bin\standalone.bat
@@ -71,7 +71,7 @@ _NOTE: The following build command assumes you have configured your Maven user s
Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#buildanddeploy) for complete
instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -96,7 +96,7 @@ The application will be running at the following URL: <http://localhost:8080/jbo
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -118,11 +118,11 @@ To run these tests, you must build the main project as described above.
mvn clean package
3. Navigate to the functional-tests/ directory in this quickstart.
-4. If you have a running instance of the JBoss Server, as described above, run the remote tests by typing the following command:
+4. 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
-5. If you prefer to run the functional tests using managed instance of the JBoss server, meaning the tests will start the
+5. 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 the following command:
mvn clean verify -Parq-jbossas-managed
View
10 spring-resteasy/README.md
@@ -30,10 +30,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
----------------------
-1. Open a command line and navigate to the root of the JBoss server directory.
+1. Open a command line and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server with the full profile:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -47,7 +47,7 @@ _NOTE: The following build command assumes you have configured your Maven user s
Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts)
for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
@@ -64,7 +64,7 @@ The application will be running at the following URL: <http://localhost:8080/jb
Run the Tests
-------------
-1. Make sure you have **started** the JBoss Server as described above and **deployed** the quickstart.
+1. Make sure you have **started** the JBoss EAP server as described above and **deployed** the quickstart.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type the following command to run the test goal with the following profile activated:
@@ -91,7 +91,7 @@ Run the Tests
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP 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:
View
30 template/README.md
@@ -1,13 +1,13 @@
QUICKSTART_NAME: Brief Description of the Quickstart
======================================================
-Author: YOUR_NAME and optional CONTACT_INFO
-Level: [one of the following: Beginner, Intermediate, or Advanced]
-Technologies: (list technologies used here)
-Summary: (a brief description of the quickstart to appear in the table )
-Prerequisites: (list any quickstarts that must be deployed prior to running this one)
-Target Product: (EAP, WFK, JDG, etc.)
-Product Versions: (EAP 6.1, EAP 6.2, WFK 2.5, etc.)
-Source: (The URL for the repository that is the source of record for this quickstart)
+Author: YOUR_NAME and optional CONTACT_INFO
+Level: [one of the following: Beginner, Intermediate, or Advanced]
+Technologies: (list technologies used here)
+Summary: (a brief description of the quickstart to appear in the table )
+Prerequisites: (list any quickstarts that must be deployed prior to running this one)
+Target Product: (EAP, WFK, JDG, etc.)
+Product Versions: (EAP 6.1, EAP 6.2, WFK 2.5, etc.)
+Source: (The URL for the repository that is the source of record for this quickstart)
_This file is meant to serve as a template or guideline for your own quickstart README.md file. Be sure to replace QUICKSTART_NAME and YOUR_NAME, with the appropriate values._
@@ -62,16 +62,16 @@ Contributor: If your quickstart requires any additional components, decribe how
* This quickstart uses Byteman to help demonstrate crash recovery. Instructions to install and configure Byteman can be found here: [Install and Configure Byteman](../README.md#install-and-configure-byteman)
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
Contributor: Does this quickstart require one or more running servers? If so, you must show how to start the server. If you start the server in one of the following 3 ways, you can simply copy the instructions in the README file located in the root folder of the quickstart directory:
- * Start the Default JBoss Server
+ * Start the Default JBoss EAP Server
- * Start the JBoss Server with the Full Profile
+ * Start the JBoss EAP Server with the Full Profile
- * St