diff --git a/README.md b/README.md index 812d657d66..0cabd4dd97 100644 --- a/README.md +++ b/README.md @@ -3,31 +3,29 @@ JBoss AS Quickstarts Summary: The quickstarts demonstrate Java EE 6 and a few additional technologies from the JBoss stack. They provide small, specific, working examples that can be used as a reference for your own project. Introduction ---------------------- +------------ These quickstarts run on both JBoss Enterprise Application Platform 6 and JBoss AS 7. If you want to run the quickstarts on JBoss Enterprise Application Platform 6, we recommend using the JBoss Enterprise Application Platform 6 ZIP file. This version uses the correct dependencies and ensures you test and compile against your runtime environment. Be sure to read this entire document before you attempt to work with the quickstarts. It contains the following information: -* [Available Quickstarts](#availableQuickstarts): List of the available quickstarts and details about each one. - -* [Suggested Approach to the Quickstarts](#suggestedApproach): A suggested approach on how to work with the quickstarts. +* [Available Quickstarts](#available-quickstarts): List of the available quickstarts and details about each one. -* [System Requirements](#systemrequirements): List of software required to run the quickstarts. +* [Suggested Approach to the Quickstarts](#suggested-approach-to-the-quickstarts): A suggested approach on how to work with the quickstarts. -* [Configure Maven](#mavenconfiguration): How to configure the Maven repository for use by the quickstarts. +* [System Requirements](#system-requirements): List of software required to run the quickstarts. -* [Run the Quickstarts](#runningquickstarts): General instructions for building, deploying, and running the quickstarts. +* [Configure Maven](#configure-maven): How to configure the Maven repository for use by the quickstarts. -* [Run the Arquillian Tests](#arquilliantests): How to run the Arquillian tests provided by some of the quickstarts. +* [Run the Quickstarts](#run-the-quickstarts): General instructions for building, deploying, and running the quickstarts. -* [Optional Components](#optionalcomponents): How to install and configure optional components required by some of the quickstarts. +* [Run the Arquillian Tests](#run-the-arquillian-tests): How to run the Arquillian tests provided by some of the quickstarts. +* [Optional Components](#optional-components): How to install and configure optional components required by some of the quickstarts. - -Available Quickstarts +Available Quickstarts --------------------- The following is a list of the currently available quickstarts. The table lists each quickstart name, the technologies it demonstrates, gives a brief description of the quickstart, and the level of experience required to set it up. For more detailed information about a quickstart, click on the quickstart name. @@ -38,9 +36,8 @@ Quickstarts with tutorials in the [Get Started Developing Applications](http://w [TOC-quickstart] - -Suggested Approach to the Quickstarts --------------------------------------- +Suggested Approach to the Quickstarts +------------------------------------- We suggest you approach the quickstarts as follows: @@ -49,9 +46,8 @@ We suggest you approach the quickstarts as follows: * Some quickstarts are based upon other quickstarts but have expanded capabilities and functionality. If a prerequisite quickstart is listed, be sure to deploy and test it before looking at the expanded version. - -System Requirements -------------- +System Requirements +------------------- To run these quickstarts with the provided build scripts, you need the following: @@ -69,17 +65,15 @@ To run these quickstarts with the provided build scripts, you need the following 3. The JBoss Enterprise Application Platform 6 distribution ZIP or the JBoss AS 7 distribution ZIP. * For information on how to install and run JBoss, refer to the product documentation. -4. You can also use [JBoss Developer Studio or Eclipse](#useeclipse) to run the quickstarts. +4. You can also use [JBoss Developer Studio or Eclipse](#use-jBoss-developer-studio-or-eclipse-to-run-the-quickstarts) to run the quickstarts. - -Configure Maven -------------- +Configure Maven +--------------- Maven configuration is dependent on whether you are using the JBoss Enterprise Application Platform 6 product version of the quickstarts or the JBoss AS7 community version of the quickstarts. - -### Configure Maven for JBoss Enterprise Application Platform 6 +### Configure Maven for JBoss Enterprise Application Platform 6 If you are using the JBoss Enterprise Application Platform 6 distribution, you need to download and configure the Maven repository. @@ -99,7 +93,6 @@ If you are using the JBoss Enterprise Application Platform 6 distribution, you n * If there is no `settings.xml` file, copy the modified `example-settings.xml` file to the `m2` directory for your operating system and rename it to `settings.xml`. - ### Configure Maven for JBoss AS 7 If you are using the JBoss AS 7 Quickstart distribution, the community artifacts are available in the Maven central repository so no additional configuration is needed. @@ -111,63 +104,63 @@ Profiles are used by Maven to customize the build environment. The `pom.xml` in * The `default` profile defines the list of modules or quickstarts that require nothing but JBoss Enterprise Application Platform or JBoss AS . * The `requires-postgres` profile lists the quickstarts that require PostgreSQL to be running when the quickstart is deployed. * The `complex-dependency` profile lists quickstarts that require manual configuration that can not be automated. -* The `requires-full` profile lists quickstarts the require you start the server using the full profile. -* The `requires-xts` profile lists quickstarts the require you start the server using the xts profile. +* The `requires-full` profile lists quickstarts the require you start the JBoss server using the full profile. +* The `requires-xts` profile lists quickstarts the require you start the JBoss server using the xts profile. * The `non-maven` profile lists quickstarts that do not require Maven, for example, quickstarts that depend on deployment of other quickstarts or those that use other Frameworks such as Forge. - -Run the Quickstarts +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](#startjboss) -* [Build and deploy the quickstart](#buildanddeploy) +* [Start the JBoss server](#start-the-jboss-server) +* [Build and deploy the quickstarts](#build-and-deploy-the-quickstarts) - -### Start the JBoss Enterprise Application Platform 6 or JBoss AS 7 Server +### Start the JBoss Server -Before you deploy a quickstart, in most cases you need a running server. A few of the Arquillian tests do not require a running server. This will be noted in the README for that quickstart. +Before you deploy a quickstart, in most cases you need a running JBoss Enterprise Application Platform 6 or JBoss AS 7server. 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. -* [Start the JBoss Server With the _web_ profile](#startserverweb): This is the default configuration. It defines minimal subsystems and services. -* [Start the JBoss Server with the _full_ profile](#startserverfull): This profile configures many of the commonly used subsystems and services. -* [Start the JBoss Server with a custom configuration](#startservercustom): Custom configuration parameters can be specified on the command line when starting the server. +* [Start the JBoss Server With the _web_ profile](#start-the-jboss-server-with-the-web-profile): 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. The README for each quickstart will specify which configuration is required to run the example. - -#### Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile +#### Start the JBoss Server with the Web Profile + +To start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile: 1. Open a command line and navigate to the root of the JBoss server directory. -2. The following shows the command line to start the server with the web profile: +2. The following shows the command line to start the JBoss server with the web profile: For Linux: JBOSS_HOME/bin/standalone.sh For Windows: JBOSS_HOME\bin\standalone.bat - -#### Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Full Profile +#### Start the JBoss Server with the Full Profile + +To start JBoss Enterprise Application Platform 6 or JBoss AS 7 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 server with the full profile: +2. The following shows the command line to start the JBoss 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 JBoss Enterprise Application Platform 6 or JBoss AS 7 with Custom Configuration Options +#### Start the JBoss Server with Custom Configuration Options + +To start JBoss Enterprise Application Platform 6 or JBoss AS 7 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 server. Replace the CUSTOM_OPTIONS with the custom optional parameters specified in the quickstart. +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. For Linux: JBOSS_HOME/bin/standalone.sh CUSTOM_OPTIONS For Windows: JBOSS_HOME\bin\standalone.bat CUSTOM_OPTIONS - -### Build and Deploy the Quickstarts +### Build and Deploy the Quickstarts See the README file in each individual quickstart folder for specific details and information on how to run and access the example. @@ -182,7 +175,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](#startjboss) as described in the README. +1. Make sure you [start the JBoss server](#start-the-jboss-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: @@ -194,15 +187,14 @@ The command to undeploy the quickstart is simply: mvn jboss-as:undeploy - ### Verify the Quickstarts Build with One Command -------------------------- +------------------------------------------------- You can verify the quickstarts build using one command. However, quickstarts that have complex dependencies must be skipped. For example, the _jax-rs-client_ quickstart is a RESTEasy client that depends on the deployment of the _helloworld-rs_ quickstart. As noted above, the root `pom.xml` file defines a `complex-dependencies` profile to exclude these quickstarts from the root build process. To build the quickstarts: -1. Do not start the server. +1. Do not start the JBoss 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: @@ -214,15 +206,14 @@ _Note_: If you see a `java.lang.OutOfMemoryError: PermGen space` error when you For Windows: SET MAVEN_OPTS=-Xmx512m - ### Undeploy the Deployed Quickstarts with One Command -------------------------- +------------------------------------------------------ To undeploy the quickstarts from the root of the quickstart folder, you must pass the argument `-fae` (fail at end) on the command line. This allows the command to continue past quickstarts that fail due to complex dependencies and quickstarts that only have Arquillian tests and do not deploy archives to the server. You can undeploy quickstarts using the following procedure: -1. Start the server. +1. Start the JBoss server. 2. Open a command line and navigate to the root directory of the quickstarts. 3. Use this command to undeploy any deployed quickstarts: @@ -231,23 +222,19 @@ You can undeploy quickstarts using the following procedure: To undeploy any quickstarts that fail due to complex dependencies, follow the undeploy procedure described in the quickstart's README file. - -### Run the Arquillian Tests -------------------------- +### Run the Arquillian Tests +---------------------------- Some of the quickstarts provide Arquillian tests. By default, these tests are configured to be skipped, as Arquillian tests require the use of a container. You can run these tests using either a remote or managed container. The quickstart README should tell you what you should expect to see in the console output and server log when you run the test. - 1. Test the quickstart on a Remote Server - * A remote container requires you start the JBoss Enterprise Application Platform 6 or JBoss AS 7 server before running the test. [Start the JBoss Server](#startjboss) as described in the quickstart README file. + * A remote container requires you start the JBoss Enterprise Application Platform 6 or JBoss AS 7 server before running the test. [Start the JBoss server](#start-the-jboss-server) as described in the quickstart README file. * Run the test goal with the following profile activated: mvn clean test -Parq-jbossas-remote - - 2. Test the quickstart on Managed Server _Note: This test requires that your server is not running. Arquillian will start the container for you, however, you must first let it know where to find the remote JBoss container._ @@ -275,25 +262,23 @@ You can run these tests using either a remote or managed container. The quicksta mvn clean test -Parq-jbossas-managed - Use JBoss Developer Studio or Eclipse to Run the Quickstarts -------------------------------------- -You can also deploy the quickstarts from Eclipse using JBoss tools. For more information on how to set up Maven and the JBoss tools, refer to the [JBoss Enterprise Application Platform 6 Development Guide](https://access.redhat.com/knowledge/docs/JBoss_Enterprise_Application_Platform/) or [Get Started Developing Applications](http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/guide/Introduction/ "Get Started Developing Applications"). +------------------------------------------------------------ +You can also deploy the quickstarts from Eclipse using JBoss tools. For more information on how to set up Maven and the JBoss tools, refer to the [JBoss Enterprise Application Platform 6 Development Guide](https://access.redhat.com/site/documentation/JBoss_Enterprise_Application_Platform/) or [Get Started Developing Applications](http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/guide/Introduction/ "Get Started Developing Applications"). - -Optional Components + +Optional Components ------------------- The following components are needed for only a small subset of the quickstarts. Do not install or configure them unless the quickstart requires it. -* [Add a User](#adduser): Add a Management or Application user for the quickstarts that run in a secured mode. +* [Add a User](#add-a-management-or-application-user): Add a Management or Application user for the quickstarts that run in a secured mode. -* [Install and Configure the PostgreSQL Database](#postgresql): The PostgreSQL database is used for the distributed transaction quickstarts. +* [Install and Configure the PostgreSQL Database](#install-and-configure-the-postgresql-database): The PostgreSQL database is used for the distributed transaction quickstarts. -* [Install and Configure Byteman](#byteman): This tool is used to demonstrate crash recovery for distributed transaction quickstarts. +* [Install and Configure Byteman](#install-and-configure-byteman): This tool is used to demonstrate crash recovery for distributed transaction quickstarts. - ### Add a Management or Application User By default, JBoss Enterprise Application Platform 6 and JBoss AS 7 are now distributed with security enabled for the management interfaces. A few of the quickstarts use these management interfaces and require that you create a management or application user to access the running application. A script is provided in the `JBOSS_HOME/bin` directory for that purpose. @@ -301,8 +286,7 @@ By default, JBoss Enterprise Application Platform 6 and JBoss AS 7 are now distr The following procedures describe how to add a user with the appropriate permissions to run the quickstarts that depend on them. - -#### Add an Management User +#### Add a Management User 1. Open a command line 2. Type the command for your operating system @@ -331,8 +315,7 @@ The following procedures describe how to add a user with the appropriate permiss 6. Choose yes for the remaining promts. - -#### Add an Application User +#### Add an Application User 1. Open a command line 2. Type the command for your operating system @@ -361,15 +344,14 @@ The following procedures describe how to add a user with the appropriate permiss 6. At the next prompt, you will be asked "What roles do you want this user to belong to?". If the quickstart README specifies a role to use, enter that here. Otherwise, type the role: `guest` - ### Install and Configure the PostgreSQL Database Some of the quickstarts require the PostgreSQL database. This section describes how to install and configure the database for use with these quickstarts. -#### Download and Install PostgreSQL 9.1.2 +#### Download and Install PostgreSQL -The following is a brief overview of how to install PostgreSQL. More detailed instructions for installing and starting PostgreSQL can be found on the internet. +The following is a brief overview of how to install PostgreSQL version 9.2. If you install a later version, be sure to modify the version when you issue the commands below. More detailed instructions for installing and starting PostgreSQL can be found on the internet. _Note_: Although the database only needs to be installed once, to help partition each quickstart we recommend using a separate database per quickstart. Where you see QUICKSTART_DATABASENAME, you should replace that with the name provided in the particular quickstart's README @@ -380,13 +362,13 @@ Use the following steps to install and configure PostgreSQL on Linux. You can do 1. Install PostgreSQL * The yum install instructions for PostgreSQL can be found here: * Download the repository RPM from here: - * To install PostgreSQL, in a command line type: + * To install PostgreSQL, in a command line type `sudo rpm -ivh RPM_FILE_NAME`, where RPM_FILE_NAME is the name of the downloaded repository RPM file, for example: - sudo rpm -ivh pgdg-fedora91-9.1-4.noarch.rpm - * Edit your distributions package manager definitions to exclude PostgreSQL. See the "important note" on for details on how to exclude postgresql packages from the repository of the distribution. - * Install _postgresql91_ and _postgres91-server_ by typing the following in a command line: + sudo rpm -ivh pgdg-fedora92-9.2-5.noarch.rpm + * Edit your distributions package manager definitions to exclude PostgreSQL. See the "important note" on for details on how to exclude install-and-configure-the-postgresql-database packages from the repository of the distribution. + * Install _postgresql92_ and _postgres92-server_ by typing the following in a command line: - sudo yum install postgresql91 postgresql91-server + sudo yum install postgresql92 postgresql92-server 2. Set a password for the _postgres_ user * In a command line, login as root and set the postgres password by typing the following commands: @@ -397,12 +379,12 @@ Use the following steps to install and configure PostgreSQL on Linux. You can do * In a command line, login as the _postgres_ user, navigate to the postgres directory, and initialize the database by typing: su postgres - cd /usr/pgsql-9.1/bin/ - ./initdb -D /var/lib/pgsql/9.1/data - * Modify the `/var/lib/pgsql/9.1/data/pg_hba.conf` file to set the authentication scheme to password for tcp connections. Modify the line following the IPv4 local connections: change trust to to password. The line should look like this: + cd /usr/pgsql-9.2/bin/ + ./initdb -D /var/lib/pgsql/9.2/data + * Modify the `/var/lib/pgsql/9.2/data/pg_hba.conf` file to set the authentication scheme to password for tcp connections. Modify the line following the IPv4 local connections: change trust to to password. The line should look like this: host all all 127.0.0.1/32 password - * Modify the `/var/lib/pgsql/9.1/data/postgresql.conf` file to allow prepared transactions and reduce the maximum number of connections + * Modify the `/var/lib/pgsql/9.2/data/postgresql.conf` file to allow prepared transactions and reduce the maximum number of connections max_prepared_transactions = 10 max_connections = 10 @@ -410,13 +392,13 @@ Use the following steps to install and configure PostgreSQL on Linux. You can do 4. Start the database server * In the same command line, type the following: - ./postgres -D /var/lib/pgsql/9.1/data + ./postgres -D /var/lib/pgsql/9.2/data * Note, this command does not release the command line. In the next step you need to open a new command line. 5. Create a database for the quickstart (as noted above, replace QUICKSTART_DATABASENAME with the name provided in the particular quickstart) * Open a new command line and login again as the _postgres_ user, navigate to the postgres directory, and create the database by typing the following: su postgres - cd /usr/pgsql-9.1/bin/ + cd /usr/pgsql-9.2/bin/ ./createdb QUICKSTART_DATABASENAME @@ -428,19 +410,19 @@ The following are the steps to install and start PostgreSQL on Mac OS X. Note th 2. Allow prepared transactions: sudo su - postgres - * Edit `/Library/PostgreSQL/9.1/data/postgresql.conf` to allow prepared transactions + * Edit `/Library/PostgreSQL/9.2/data/postgresql.conf` to allow prepared transactions max_prepared_transactions = 10 3. Start the database server - cd /Library/PostgreSQL/9.1/bin + cd /Library/PostgreSQL/9.2/bin ./pg_ctl -D ../data restart 4. Create a database for the quickstart (as noted above, replace QUICKSTART_DATABASENAME with the name provided in the particular quickstart) ./createdb QUICKSTART_DATABASENAME 5. Verify that everything works. As the _postgres_ user using the password you specified in Step 1, type the following: - cd /Library/PostgreSQL/9.1/bin + cd /Library/PostgreSQL/9.2/bin ./psql -U postgres At the prompt @@ -456,22 +438,22 @@ Use the following steps to install and configure PostgreSQL on Windows: 1. Install PostgreSQL using the Windows installer: 2. Enable password authentication and configure PostgreSQL to allow prepared transactions - * Modify the `C:\Program Files\PostgreSQL\9.1\data\pg_hba.conf` file to set the authentication scheme to password for tcp connections. Modify the line following the IPv4 local connections: change trust to to password. The line should look like this: + * Modify the `C:\Program Files\PostgreSQL\9.2\data\pg_hba.conf` file to set the authentication scheme to password for tcp connections. Modify the line following the IPv4 local connections: change trust to to password. The line should look like this: host all all 127.0.0.1/32 password` - * Modify the `C:\Program Files\PostgreSQL\9.1\data\postgresql.conf` file to allow prepared transactions and reduce the maximum number of connections: + * Modify the `C:\Program Files\PostgreSQL\9.2\data\postgresql.conf` file to allow prepared transactions and reduce the maximum number of connections: max_prepared_transactions = 10 max_connections = 10 3. Start the database server - * Choose Start -> All Programs -> PostgreSQL 9.1\pgAdmin III - * Server Groups -> Servers (1) -> PostgreSQL 9.1 (localhost:5432) + * Choose Start -> All Programs -> PostgreSQL 9.2\pgAdmin III + * Server Groups -> Servers (1) -> PostgreSQL 9.2 (localhost:5432) * Right click -> Stop Service * Right click -> Start Service 4. Create a database for the quickstart (as noted above, replace QUICKSTART_DATABASENAME with the name provided in the particular quickstart) * Open a command line - cd C:\Program Files\PostgreSQL\9.1\bin\ + cd C:\Program Files\PostgreSQL\9.2\bin\ createdb.exe -U postgres QUICKSTART_DATABASENAME @@ -493,8 +475,6 @@ Use the following steps to install and configure PostgreSQL on Windows: psql -h 127.0.0.1 -U sa QUICKSTART_DATABASENAME - - #### Add the PostgreSQL Module to the JBoss server 1. Create the following directory structure: `JBOSS_HOME/modules/org/postgresql/main` @@ -504,7 +484,7 @@ Use the following steps to install and configure PostgreSQL on Windows: - + @@ -512,9 +492,7 @@ Use the following steps to install and configure PostgreSQL on Windows: - - -#### Add the Driver Configuration to the JBoss server +#### Add the PostgreSQL Driver Configuration to the JBoss server You can configure the driver by running the `configure-postgresql.cli` script provided in the root directory of the quickstarts, by using the JBoss CLI interactively, or by manually editing the configuration file. @@ -527,7 +505,7 @@ _NOTE - Before you begin:_ ##### Configure the Driver By Running the JBoss CLI Script -1. Start the JBoss Enterprise Application Platform 6 or JBoss AS 7 Server by typing the following: +1. Start the JBoss Enterprise Application Platform 6 or JBoss AS 7 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 @@ -543,7 +521,7 @@ This script adds the PostgreSQL driver to the datasources subsystem in the serve ##### Configure the Driver Using the JBoss CLI Interactively -1. Start the JBoss Enterprise Application Platform 6 or JBoss AS 7 Server by typing the following: +1. Start the JBoss Enterprise Application Platform 6 or JBoss AS 7 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 @@ -574,7 +552,7 @@ When you are done testing the quickstarts, you can remove the PostgreSQL configu ##### Remove the PostgreSQL Configuration by Running the JBoss CLI Script -1. Start the JBoss Enterprise Application Platform 6 or JBoss AS 7 Server by typing the following: +1. Start the JBoss Enterprise Application Platform 6 or JBoss AS 7 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 @@ -599,8 +577,7 @@ This script removes PostgreSQL from the `datasources` subsystem in the server co The installation of PostgreSQL is a one time procedure. However, unless you have set up the database to automatically start as a service, you must repeat the instructions "Start the database server" above for your operating system every time you reboot your machine. - -### Install and Configure Byteman +### Install and Configure Byteman _Byteman_ is used by a few of the quickstarts to demonstrate distributed transaction processing and crash recovery. @@ -608,7 +585,6 @@ _Byteman_ is used by a few of the quickstarts to demonstrate distributed transac _Byteman_ is a tool which simplifies tracing and testing of Java programs. Byteman allows you to insert extra Java code into your application, either as it is loaded during JVM startup or after it has already started running. This code can be used to trace what the application is doing and to monitor and debug deployments to be sure it is operating correctly. You can also use _Byteman_ to inject faults or synchronization code when testing your application. A few of the quickstarts use _Byteman_ to halt an application server in the middle of a distributed transaction to demonstrate crash recovery. - #### Download and Configure Byteman 1. Download Byteman from @@ -618,10 +594,9 @@ _Byteman_ is a tool which simplifies tracing and testing of Java programs. Bytem cd byteman-download-2.0.0/ chmod -R o-rwx byteman-download-2.0.0/ - #### Halt the Application Using Byteman -_NOTE_: The Byteman scripts only work in JTA mode. They do not work in JTS mode. If you have configured the server for a JTS quickstart, you must follow the instructions to [Remove the JTS Configuration from the JBoss server](jts/README.md#remove-jts-configuration) before making the following changes. Otherwise Byteman will not halt the server. +_NOTE_: The Byteman scripts only work in JTA mode. They do not work in JTS mode. If you have configured the server for a JTS quickstart, you must follow the instructions to [Remove the JTS Configuration from the JBoss server](jts/README.md#remove-the-jts-configuration-from-the-jboss-server) before making the following changes. Otherwise Byteman will not halt the server. When instructed to use Byteman to halt the application, perform the following steps: @@ -645,7 +620,6 @@ When instructed to use Byteman to halt the application, perform the following st SET "JAVA_OPTS=%JAVA_OPTS% -javaagent:C:PATH_TO_BYTEMAN_DOWNLOAD\lib\byteman.jar=script:C:\PATH_TO_QUICKSTARTS\jta-crash-rec\src\main\scripts\xa.btm %JAVA_OPTS%" - #### Disable the Byteman Script diff --git a/RELEASE_PROCEDURE.md b/RELEASE_PROCEDURE.md index 67d08e4fb9..bbbf9efd80 100644 --- a/RELEASE_PROCEDURE.md +++ b/RELEASE_PROCEDURE.md @@ -57,7 +57,7 @@ Then just run Publishing builds to Maven -------------------------- - 1. You must have gpg set up and your key registered, as described at + 1. You must have gpg set up and your key registered, as described at 2. You must provide a property `gpg.passphrase` in your `settings.xml` in the `release` profile e.g. diff --git a/bean-validation/README.md b/bean-validation/README.md index 9720d80e13..6521ebb49e 100644 --- a/bean-validation/README.md +++ b/bean-validation/README.md @@ -26,7 +26,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -44,7 +44,7 @@ Run the Arquillian Tests This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container. -_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#arquilliantests) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -75,7 +75,7 @@ You can also check the server console output to verify that the Arquillian tests Test the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/bmt/README.md b/bmt/README.md index 54d2ee3122..ef7a0d331d 100644 --- a/bmt/README.md +++ b/bmt/README.md @@ -34,7 +34,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -50,7 +50,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -85,7 +85,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/carmart-tx/README.md b/carmart-tx/README.md index e264962e82..0c8d603507 100644 --- a/carmart-tx/README.md +++ b/carmart-tx/README.md @@ -38,7 +38,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#configure-maven-) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 @@ -54,7 +54,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 Build and Deploy the Application in Library Mode ------------------------------------------------ -_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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. diff --git a/carmart/README.md b/carmart/README.md index 250bd28beb..363b591152 100644 --- a/carmart/README.md +++ b/carmart/README.md @@ -32,7 +32,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#configure-maven-) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 @@ -48,7 +48,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 Build and Deploy the Application in Library Mode ----------------------------------------------- -_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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. diff --git a/cdi-add-interceptor-binding/README.md b/cdi-add-interceptor-binding/README.md index 0c18bdc61e..a6eeb71303 100644 --- a/cdi-add-interceptor-binding/README.md +++ b/cdi-add-interceptor-binding/README.md @@ -37,7 +37,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile ------------------------- @@ -54,7 +54,7 @@ Run the Arquillian Tests This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container. -_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#arquilliantests) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -74,7 +74,7 @@ managed server or 'arq-jbossas-remote' for running on remote server. To run the tests, right click on the project or individual classes and select Run As --> JUnit Test in the context menu. -For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Investigate the Console Output ---------------------------- diff --git a/cdi-alternative/README.md b/cdi-alternative/README.md index e33c9ae6bf..66d9d1895c 100644 --- a/cdi-alternative/README.md +++ b/cdi-alternative/README.md @@ -35,7 +35,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 @@ -51,7 +51,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -87,7 +87,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application ------------------------------------ diff --git a/cdi-decorator/README.md b/cdi-decorator/README.md index ce64ffe8dc..6e99bfa5c9 100644 --- a/cdi-decorator/README.md +++ b/cdi-decorator/README.md @@ -27,7 +27,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 @@ -43,7 +43,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -82,7 +82,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application ------------------------------------ diff --git a/cdi-injection/README.md b/cdi-injection/README.md index 01bac40df0..5cfa6726d4 100644 --- a/cdi-injection/README.md +++ b/cdi-injection/README.md @@ -23,7 +23,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -39,7 +39,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -68,7 +68,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/cdi-interceptors/README.md b/cdi-interceptors/README.md index 354e72aea5..ea349f8c46 100644 --- a/cdi-interceptors/README.md +++ b/cdi-interceptors/README.md @@ -25,7 +25,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -41,7 +41,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -81,7 +81,7 @@ Run the Arquillian Tests This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container. -_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#arquilliantests) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -92,7 +92,7 @@ _NOTE: The following commands assume you have configured your Maven user setting Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/cdi-portable-extension/README.md b/cdi-portable-extension/README.md index 7b0e947c58..4ef8c20177 100644 --- a/cdi-portable-extension/README.md +++ b/cdi-portable-extension/README.md @@ -38,7 +38,7 @@ Configure Maven Contributor: You can copy or link to the Maven configuration information in the README file in the root folder of the quickstarts. For example: -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile ------------------------- @@ -55,7 +55,7 @@ Run the Arquillian Tests This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container. -_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#arquilliantests) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -120,7 +120,7 @@ The two statements to look for are these: Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/cdi-stereotype/README.md b/cdi-stereotype/README.md index 94768fffdc..11012971d5 100644 --- a/cdi-stereotype/README.md +++ b/cdi-stereotype/README.md @@ -30,7 +30,7 @@ Note: The quickstart does not work on JBoss 7.1.1, since it includes old weld li Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6.01 or higher with the Web Profile @@ -46,7 +46,7 @@ Start JBoss Enterprise Application Platform 6.01 or higher with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -83,7 +83,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/cdi-veto/README.md b/cdi-veto/README.md index 02151dccbd..1bae4791d9 100644 --- a/cdi-veto/README.md +++ b/cdi-veto/README.md @@ -37,7 +37,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile ------------------------- @@ -54,7 +54,7 @@ Run the Arquillian Tests This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container. -_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#arquilliantests) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -96,7 +96,7 @@ That will let you know the extension is working. To really see what's going on a Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/cluster-ha-singleton/README.md b/cluster-ha-singleton/README.md index d54267b52b..10ece3c015 100644 --- a/cluster-ha-singleton/README.md +++ b/cluster-ha-singleton/README.md @@ -34,7 +34,7 @@ Configure Maven You can copy or link to the Maven configuration information in the README file in the root folder of the quickstarts. For example: -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with a HA profile @@ -50,7 +50,7 @@ should be started. 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -65,36 +65,34 @@ _NOTE: The following build command assumes you have configured your Maven user s 6. This will deploy `service/target/jboss-as-cluster-ha-singleton-service.jar` to the running instance of the additional server. -Check whether the application is deployed on each instance. -All instances will have a message: -INFO [org.jboss.as.clustering.singleton] (SingletonService lifecycle - 1) JBAS010342: nodeOne/cluster elected as the singleton provider of the jboss.quickstart.ejb.ha.singleton service -Only nodeOne (or even one instance) will have a message: -INFO [org.jboss.as.clustering.singleton] (SingletonService lifecycle - 1) JBAS010340: This node will now operate as the singleton provider of the jboss.quickstart.ejb.ha.singleton service +7. Check whether the application is deployed on each instance. All instances will have a message: -The timer on the started node will log a message every 10sec. + INFO [org.jboss.as.clustering.singleton] (SingletonService lifecycle - 1) JBAS010342: nodeOne/cluster elected as the singleton provider of the jboss.quickstart.ejb.ha.singleton service + Only nodeOne (or even one instance) will have a message: + INFO [org.jboss.as.clustering.singleton] (SingletonService lifecycle - 1) JBAS010340: This node will now operate as the singleton provider of the jboss.quickstart.ejb.ha.singleton service +8. The timer on the started node will log a message every 10sec. Check the timer --------------------- 1. Open a command line and navigate to the root directory of this quickstart. -2. Type this command to start the client +2. Type the following command to start the client: cd client mvn exec:exec -3. check the output - The request to the EJB is running four times and every time it should answer - # The timer service is active on node with name = NodeOne - If you look into the servers logfiles you will see that each node will process requests -4. Stop the server nodeOne - If you look into the server nodeTwo logfile you will see the message - "JBAS010342: nodeTwo/cluster elected as the singleton provider of ..." - that shows that the singleton service was started here - The timer will be started here and log a message every 10sec. -5. repeat step 2 - The request is running four times and the message is - # The timer service is active on node with name = NodeTwo - If you look into the server#2 logfile you will see that it process all four requests. +3. Check the output. The request to the EJB is running four times and every time it should respond: + + # The timer service is active on node with name = NodeOne + If you look in the server log files, you will see that each node will process requests +4. Stop the server `nodeOne`. If you look into the server `nodeTwo` log file, you will see the message: + + JBAS010342: nodeTwo/cluster elected as the singleton provider of ..." + This shows that the singleton service was started. The timer will be started here and log a message every 10 seconds. +5. Repeat step 2. The request is running four times and the message is: + + # The timer service is active on node with name = NodeTwo + If you look into the server #2 log file you will see that it process all four requests. Undeploy the Archive @@ -110,7 +108,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application ------------------------------------ diff --git a/cmt/README.md b/cmt/README.md index d8ad90ce61..99687f149b 100644 --- a/cmt/README.md +++ b/cmt/README.md @@ -53,19 +53,19 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Configure the application server to use PostgreSQL -------------------------------------------------- -This quickstart requires the PostgreSQL database. Instructions to install an configure PostgreSQL can be found here: [Install and Configure the PostgreSQL Database](../README.md#postgresql) +This quickstart requires the PostgreSQL database. Instructions to install an configure PostgreSQL can be found here: [Install and Configure the PostgreSQL Database](../README.md#install-and-configure-the-postgresql-database) _Note_: For the purpose of this quickstart, replace the word QUICKSTART_DATABASENAME with `cmt-quickstart-database` in the PostgreSQL instructions. 1. Be sure to start the PostgreSQL database. Unless you have set up the database to automatically start as a service, you must repeat the instructions "Start the database server" for your operating system every time you reboot your machine. -2. [Add the PostgreSQL Module](../README.md#addpostgresqlmodule) to the JBoss server `modules/` directory. -3. [Add the PostgreSQL driver](../README.md#addpostgresqldriver) to the JBoss server configuration file. +2. [Add the PostgreSQL Module](../README.md#add-the-postgresql-module-to-the-jboss-server) to the JBoss server `modules/` directory. +3. [Add the PostgreSQL driver](../README.md#add-the-postgresql-driver-configuration-to-the-jboss-server) to the JBoss server configuration file. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Full Profile --------------- @@ -80,7 +80,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Full Profil 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#buildanddeploy) for complete instructions and additional options._ +_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 with the PostgreSQL driver @@ -93,7 +93,6 @@ _NOTE: The following build command assumes you have configured your Maven user s Access the application --------------------- -To access the application type the following into a browser: The application will be running at the following URL: . @@ -116,7 +115,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/deltaspike-authorization/README.md b/deltaspike-authorization/README.md index b1211d4a20..2b3b2b9fcd 100644 --- a/deltaspike-authorization/README.md +++ b/deltaspike-authorization/README.md @@ -33,12 +33,12 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. 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#addapplicationuser) +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 JBoss Enterprise Application Platform 6 or JBoss AS 7 @@ -53,7 +53,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -87,7 +87,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application ------------------------------------ diff --git a/deltaspike-beanbuilder/README.md b/deltaspike-beanbuilder/README.md index 2bf3eac7ea..1053b57c1f 100644 --- a/deltaspike-beanbuilder/README.md +++ b/deltaspike-beanbuilder/README.md @@ -29,7 +29,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile ------------------------- @@ -46,7 +46,7 @@ Run the Arquillian Tests This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container. -_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#arquilliantests) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -90,7 +90,7 @@ Maven prints summary of performed tests into the console: Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/deltaspike-beanmanagerprovider/README.md b/deltaspike-beanmanagerprovider/README.md index 3a06125955..504476e9d2 100644 --- a/deltaspike-beanmanagerprovider/README.md +++ b/deltaspike-beanmanagerprovider/README.md @@ -29,7 +29,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 @@ -45,7 +45,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -85,7 +85,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application ------------------------------------ diff --git a/deltaspike-deactivatable/README.md b/deltaspike-deactivatable/README.md index d8989cc595..5fa01b4613 100644 --- a/deltaspike-deactivatable/README.md +++ b/deltaspike-deactivatable/README.md @@ -26,7 +26,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile ------------------------- @@ -43,7 +43,7 @@ Run the Arquillian Tests This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container. -_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#arquilliantests) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -69,51 +69,50 @@ Investigate the Console Output ### Maven -------------------------------------------------------- - T E S T S -------------------------------------------------------- -Running org.jboss.as.quickstart.deltaspike.beanbuilder.test.DeactivatableTest -log4j:WARN No appenders could be found for logger (org.jboss.logging). -log4j:WARN Please initialize the log4j system properly. -Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.745 sec + ------------------------------------------------------- + T E S T S + ------------------------------------------------------- + Running org.jboss.as.quickstart.deltaspike.beanbuilder.test.DeactivatableTest + log4j:WARN No appenders could be found for logger (org.jboss.logging). + log4j:WARN Please initialize the log4j system properly. + Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.745 sec -Results : + Results : -Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 + Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 ### Server log -There is a logging statements done when the tests are run: - -#### Example - -15:36:34,065 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "deactivator.war" -15:36:34,632 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment deactivator.war -15:36:34,719 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016005: Starting Services for CDI deployment: deactivator.war -15:36:34,726 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016008: Starting weld service for deployment deactivator.war -15:36:34,849 INFO [org.apache.deltaspike.core.impl.config.EnvironmentPropertyConfigSourceProvider] (MSC service thread 1-3) Custom config found by DeltaSpike. Name: 'META-INF/apache-deltaspike.properties', URL: 'vfs:/content/deactivator.war/WEB-INF/classes/META-INF/apache-deltaspike.properties' -15:36:34,860 INFO [org.apache.deltaspike.core.util.ClassDeactivationUtils] (MSC service thread 1-3) class: org.apache.deltaspike.core.impl.config.ConfigurationExtension activated=true -15:36:34,861 INFO [org.apache.deltaspike.core.util.ClassDeactivationUtils] (MSC service thread 1-3) class: org.apache.deltaspike.core.impl.exclude.extension.ExcludeExtension activated=false -15:36:34,864 INFO [org.apache.deltaspike.core.util.ClassDeactivationUtils] (MSC service thread 1-3) class: org.apache.deltaspike.core.impl.exclude.GlobalAlternative activated=true -15:36:34,867 INFO [org.apache.deltaspike.core.util.ClassDeactivationUtils] (MSC service thread 1-3) class: org.apache.deltaspike.core.impl.exclude.CustomProjectStageBeanFilter activated=true -15:36:34,868 INFO [org.apache.deltaspike.core.util.ClassDeactivationUtils] (MSC service thread 1-3) class: org.apache.deltaspike.core.impl.exception.control.extension.ExceptionControlExtension activated=true -15:36:34,868 INFO [org.apache.deltaspike.core.util.ClassDeactivationUtils] (MSC service thread 1-3) class: org.apache.deltaspike.core.impl.message.MessageBundleExtension activated=true -15:36:35,978 INFO [org.apache.deltaspike.core.util.ProjectStageProducer] (MSC service thread 1-3) Computed the following DeltaSpike ProjectStage: Production -15:36:36,026 INFO [org.jboss.web] (MSC service thread 1-4) JBAS018210: Registering web context: /deactivator -15:36:36,164 INFO [org.jboss.as.server] (management-handler-thread - 42) JBAS018559: Deployed "deactivator.war" -15:36:37,510 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016009: Stopping weld service for deployment deactivator.war -15:36:37,566 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment deactivator.war in 70ms -15:36:37,685 INFO [org.jboss.as.repository] (management-handler-thread - 43) JBAS014901: Content removed from location /java/tools/jboss-as-7.1.1.Final/standalone/data/content/db/87621f007d7af7741881722f7d3c152f6648f0/content -15:36:37,686 INFO [org.jboss.as.server] (management-handler-thread - 43) JBAS018558: Undeployed "deactivator.war" +When the tests are run, statements are written to the server log as follows: + + 15:36:34,065 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "deactivator.war" + 15:36:34,632 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment deactivator.war + 15:36:34,719 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016005: Starting Services for CDI deployment: deactivator.war + 15:36:34,726 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016008: Starting weld service for deployment deactivator.war + 15:36:34,849 INFO [org.apache.deltaspike.core.impl.config.EnvironmentPropertyConfigSourceProvider] (MSC service thread 1-3) Custom config found by DeltaSpike. Name: 'META-INF/apache-deltaspike.properties', URL: 'vfs:/content/deactivator.war/WEB-INF/classes/META-INF/apache-deltaspike.properties' + 15:36:34,860 INFO [org.apache.deltaspike.core.util.ClassDeactivationUtils] (MSC service thread 1-3) class: org.apache.deltaspike.core.impl.config.ConfigurationExtension activated=true + 15:36:34,861 INFO [org.apache.deltaspike.core.util.ClassDeactivationUtils] (MSC service thread 1-3) class: org.apache.deltaspike.core.impl.exclude.extension.ExcludeExtension activated=false + 15:36:34,864 INFO [org.apache.deltaspike.core.util.ClassDeactivationUtils] (MSC service thread 1-3) class: org.apache.deltaspike.core.impl.exclude.GlobalAlternative activated=true + 15:36:34,867 INFO [org.apache.deltaspike.core.util.ClassDeactivationUtils] (MSC service thread 1-3) class: org.apache.deltaspike.core.impl.exclude.CustomProjectStageBeanFilter activated=true + 15:36:34,868 INFO [org.apache.deltaspike.core.util.ClassDeactivationUtils] (MSC service thread 1-3) class: org.apache.deltaspike.core.impl.exception.control.extension.ExceptionControlExtension activated=true + 15:36:34,868 INFO [org.apache.deltaspike.core.util.ClassDeactivationUtils] (MSC service thread 1-3) class: org.apache.deltaspike.core.impl.message.MessageBundleExtension activated=true + 15:36:35,978 INFO [org.apache.deltaspike.core.util.ProjectStageProducer] (MSC service thread 1-3) Computed the following DeltaSpike ProjectStage: Production + 15:36:36,026 INFO [org.jboss.web] (MSC service thread 1-4) JBAS018210: Registering web context: /deactivator + 15:36:36,164 INFO [org.jboss.as.server] (management-handler-thread - 42) JBAS018559: Deployed "deactivator.war" + 15:36:37,510 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016009: Stopping weld service for deployment deactivator.war + 15:36:37,566 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment deactivator.war in 70ms + 15:36:37,685 INFO [org.jboss.as.repository] (management-handler-thread - 43) JBAS014901: Content removed from location /java/tools/jboss-as-7.1.1.Final/standalone/data/content/db/87621f007d7af7741881722f7d3c152f6648f0/content + 15:36:37,686 INFO [org.jboss.as.server] (management-handler-thread - 43) JBAS018558: Undeployed "deactivator.war" The log statement to look for is this: -15:36:34,861 INFO [org.apache.deltaspike.core.util.ClassDeactivationUtils] (MSC service thread 1-3) class: org.apache.deltaspike.core.impl.exclude.extension.ExcludeExtension activated=false + 15:36:34,861 INFO [org.apache.deltaspike.core.util.ClassDeactivationUtils] (MSC service thread 1-3) class: org.apache.deltaspike.core.impl.exclude.extension.ExcludeExtension activated=false Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) + +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/deltaspike-exception-handling/README.md b/deltaspike-exception-handling/README.md index 647260beff..cb1effa366 100644 --- a/deltaspike-exception-handling/README.md +++ b/deltaspike-exception-handling/README.md @@ -37,7 +37,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 @@ -53,7 +53,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -87,7 +87,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application ------------------------------------ diff --git a/deltaspike-helloworld-jms/README.md b/deltaspike-helloworld-jms/README.md index 42fa1c8a76..4f0c3eedd2 100644 --- a/deltaspike-helloworld-jms/README.md +++ b/deltaspike-helloworld-jms/README.md @@ -30,12 +30,12 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. 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#addapplicationuser) +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 Enterprise Application Platform 6 server @@ -115,7 +115,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Full Profil 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -162,13 +162,13 @@ The following properties can be configured: * `username` - This username is used for both the JMS connection and the JNDI look-up. Instructions to set up the quickstart application user can be found here: [Add an Application User](../README.md#addapplicationuser). + This username is used for both the JMS connection and the JNDI look-up. Instructions to set up the quickstart application user can be found here: [Add an Application User](../README.md#add-an-application-user). Default: `quickstartUser` * `password` - This password is used for both the JMS connection and the JNDI look-up. Instructions to set up the quickstart application user can be found here: [Add an Application User](../README.md#addapplicationuser) + This password is used for both the JMS connection and the JNDI look-up. Instructions to set up the quickstart application user can be found here: [Add an Application User](../README.md#add-an-application-user) Default: `quickstartPwd1!` @@ -243,7 +243,7 @@ This script removes the `test` queue from the `messaging` subsystem in the serve Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application ------------------------------------ diff --git a/deltaspike-projectstage/README.md b/deltaspike-projectstage/README.md index 7d952ec9fd..cd58a5f56c 100644 --- a/deltaspike-projectstage/README.md +++ b/deltaspike-projectstage/README.md @@ -42,7 +42,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 @@ -57,7 +57,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -94,7 +94,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application ------------------------------------ diff --git a/dist/github-flavored-markdown.rb b/dist/github-flavored-markdown.rb index b0ad046d62..da091231ba 100755 --- a/dist/github-flavored-markdown.rb +++ b/dist/github-flavored-markdown.rb @@ -43,7 +43,7 @@ def header(title, level) element.to_s end end - permalink = flattened_title.downcase.gsub(/[^a-z\s]/, '').gsub(/\W+/, "-") + permalink = flattened_title.downcase.gsub(/[^a-z0-9\s]/, '').gsub(/\W+/, "-") # for extra credit: implement this as its own method if @headers.include?(permalink) diff --git a/ejb-asynchronous/README.md b/ejb-asynchronous/README.md index 9534949efd..54f7f453ba 100644 --- a/ejb-asynchronous/README.md +++ b/ejb-asynchronous/README.md @@ -33,7 +33,7 @@ Configure Maven You can copy or link to the Maven configuration information in the README file in the root folder of the quickstarts. For example: -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 @@ -46,7 +46,7 @@ Start a server instance 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -99,7 +99,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application ------------------------------------ diff --git a/ejb-in-ear/README.md b/ejb-in-ear/README.md index dff75324a4..b7a87c33cd 100644 --- a/ejb-in-ear/README.md +++ b/ejb-in-ear/README.md @@ -42,7 +42,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven ------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -58,7 +58,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -90,7 +90,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/ejb-in-war/README.md b/ejb-in-war/README.md index 5038b9d803..78e61b1d0c 100644 --- a/ejb-in-war/README.md +++ b/ejb-in-war/README.md @@ -31,7 +31,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven ------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -47,7 +47,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -79,7 +79,7 @@ Run the Arquillian Tests This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container. -_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#arquilliantests) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -110,7 +110,7 @@ Search for lines similar to the following ones in the server output log: Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/ejb-remote/README.md b/ejb-remote/README.md index 359bca7cfb..8217ea7679 100644 --- a/ejb-remote/README.md +++ b/ejb-remote/README.md @@ -35,7 +35,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -168,7 +168,7 @@ To undeploy the server side component from the JBoss server: Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/ejb-security-interceptors/README.md b/ejb-security-interceptors/README.md index 278566656c..76b569ab48 100644 --- a/ejb-security-interceptors/README.md +++ b/ejb-security-interceptors/README.md @@ -71,7 +71,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Prerequisites ------------- @@ -260,7 +260,7 @@ The first user establishes the actual connection to the server. The subsequent t Also do note that within the quickstart we do not make use of the passwords for any of the 'App' users, the passwords specified for those users are a suggestion for values that will be accepted by the ass-user utility. -For an example of how to use the add-user utility, see instructions in the root README file located here: [Add User](../README.md#addapplicationuser). +For an example of how to use the add-user utility, see instructions in the root README file located here: [Add an Application User](../README.md#add-an-application-user). ### Add Users Manually @@ -296,7 +296,7 @@ Start JBoss Enterprise Application Platform 6.1 or JBoss AS 7.2 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -522,7 +522,7 @@ This script removes the `test` queue from the `messaging` subsystem in the serve Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/ejb-security-plus/README.md b/ejb-security-plus/README.md index 6ac54edcc6..82dbff9c94 100644 --- a/ejb-security-plus/README.md +++ b/ejb-security-plus/README.md @@ -62,7 +62,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Prerequisites ------------- @@ -174,7 +174,7 @@ This quickstart is built around the default `ApplicationRealm` as configured in This user is used to both connect to the server and is used for the actual EJB invocation. -For an example of how to use the add-user utility, see instructions in the root README file located here: [Add User](../README.md#addapplicationuser). +For an example of how to use the add-user utility, see instructions in the root README file located here: [Add User](../README.md#add-an-application-user). ### Add Users Manually @@ -204,7 +204,7 @@ Start JBoss Enterprise Application Platform 6.1 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -287,7 +287,7 @@ This script removes the `test` queue from the `messaging` subsystem in the serve Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/ejb-security/README.md b/ejb-security/README.md index 5f41d0a159..09fbcff3aa 100644 --- a/ejb-security/README.md +++ b/ejb-security/README.md @@ -46,13 +46,13 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Add the Application Users --------------- -This quickstart uses a secured management interface and requires that you create an application user to access the running application. Instructions to set up an Application user can be found here: [Add an Application User](../README.md#addapplicationuser) +This quickstart uses a secured management interface and requires that you create an application user to access the running application. Instructions to set up an Application user can be found here: [Add an Application User](../README.md#add-an-application-user) After you add the default `quickstartUser`, use the same steps to add a second application user who is not in the `guest` role and therefore is not authorized to access the application. @@ -74,7 +74,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -132,7 +132,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/ejb-throws-exception/README.md b/ejb-throws-exception/README.md index 85c6ea8ff7..3d7c4f59db 100644 --- a/ejb-throws-exception/README.md +++ b/ejb-throws-exception/README.md @@ -44,7 +44,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven ------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -60,7 +60,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -96,7 +96,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/forge-from-scratch/README.md b/forge-from-scratch/README.md index c05782d39e..d9e8ca7b06 100644 --- a/forge-from-scratch/README.md +++ b/forge-from-scratch/README.md @@ -69,7 +69,7 @@ For a full description of what was generated by running this script and details Configure Maven ------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. _NOTE: If you are using JBoss Enterprise Application Platform 6, you can not append the path to the Maven settings on the Forge command line. You must configure the Maven user settings as noted in step 4 of the instructions._ @@ -129,7 +129,7 @@ Play around with creating more entities, relationships, UI, and generating JAX-R Explore plugins! ---------------- -Forge has a rich plugin ecosystem. Want to deploy your application to the Cloud? Use the Forge Openshift Express plugin: http://github.com/forge/plugin-openshift-express/ +Forge has a rich plugin ecosystem. Want to deploy your application to the Cloud? Use the Forge Openshift plugin: http://github.com/forge/plugin-openshift/ To see a full list of avaialable plugins, make sure that you have an active internet connection and type: @@ -139,7 +139,7 @@ To see a full list of avaialable plugins, make sure that you have an active inte Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/greeter-spring/README.md b/greeter-spring/README.md index b8f472473d..240c1c9621 100644 --- a/greeter-spring/README.md +++ b/greeter-spring/README.md @@ -56,7 +56,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -86,7 +86,7 @@ Or you can manually remove the application by removing greeter-spring.war from J Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application ------------------------------------ diff --git a/greeter/README.md b/greeter/README.md index 62e6097222..b152599724 100644 --- a/greeter/README.md +++ b/greeter/README.md @@ -37,7 +37,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -53,7 +53,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -82,7 +82,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/h2-console/README.md b/h2-console/README.md index 0139d0ebe9..19980c3446 100644 --- a/h2-console/README.md +++ b/h2-console/README.md @@ -26,7 +26,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Prerequisites diff --git a/helloworld-errai/README.md b/helloworld-errai/README.md index ad47439d82..7bd6af3d3d 100644 --- a/helloworld-errai/README.md +++ b/helloworld-errai/README.md @@ -27,7 +27,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -43,7 +43,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -84,7 +84,7 @@ GWT Dev Mode provides an edit-save-refresh development experience. If you plan t Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/helloworld-gwt/README.md b/helloworld-gwt/README.md index f170d55b2b..ee4edd4781 100644 --- a/helloworld-gwt/README.md +++ b/helloworld-gwt/README.md @@ -26,7 +26,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -42,7 +42,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -83,7 +83,7 @@ GWT Dev Mode provides an edit-save-refresh development experience. If you plan t Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/helloworld-html5/README.md b/helloworld-html5/README.md index 54a3b970f3..7c0b7d1a3e 100644 --- a/helloworld-html5/README.md +++ b/helloworld-html5/README.md @@ -23,15 +23,20 @@ All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven The application this project produces is designed to be run on JBoss AS 7 or JBoss Enterprise Application Platform 6. -An HTML5 compatible browser such as Chrome, Safari 5+, Firefox 5+, or IE 9+ are -required. +An HTML5 compatible browser such as Chrome, Safari 5+, Firefox 5+, or IE 9+ is required. With the prerequisites out of the way, you're ready to build and deploy. -Deploying the application +Configure Maven +--------------- + +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. + + +Deploy the Application ------------------------- -### Deploying locally +### Deploy the Application locally First you need to start the JBoss container. To do this, run @@ -58,26 +63,25 @@ To undeploy run this command: mvn jboss-as:undeploy -You can also start the JBoss container and deploy the project using JBoss Tools. See the -Getting Started Developing Applications Guide -for more information. +You can also start the JBoss container and deploy the project using JBoss Tools. See the [Get Started Developing Applications Guide](http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/guide/Introduction/ "Get Started Developing Applications") for more information. + -### Deploying to OpenShift +### Deploy the Application to OpenShift You can also deploy the application directly to OpenShift, Red Hat's cloud based PaaS offering, follow the instructions [here](https://community.jboss.org/wiki/DeployingHTML5ApplicationsToOpenshift) -Importing the project into an IDE +Import the Project into an IDE ================================= -Detailed instructions for using Eclipse / JBoss Tools with are provided in the -Getting Started Developing Applications Guide. +Detailed instructions for using Eclipse / JBoss Tools with are provided in the [Get Started Developing Applications](http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/guide/Introduction/ "Get Started Developing Applications"). + If you created the project from the commandline using archetype:generate, then you need to import the project into your IDE. If you are using NetBeans 6.8 or IntelliJ IDEA 9, then all you have to do is open the project as an existing project. Both of these IDEs recognize Maven projects natively. -Downloading the sources and Javadocs +Download the Source and Javadocs ==================================== If you want to be able to debug into the source code or look at the Javadocs diff --git a/helloworld-jdg/README.md b/helloworld-jdg/README.md index df552ed155..78b232b77e 100644 --- a/helloworld-jdg/README.md +++ b/helloworld-jdg/README.md @@ -33,7 +33,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start first instance of JBoss Enterprise Application Platform 6 or JBoss AS 7 @@ -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#buildanddeploy) +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 both instances of the JBoss Server as described above. @@ -120,7 +120,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------------------------- You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, -see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/helloworld-jms/README.md b/helloworld-jms/README.md index e0f48bb5f7..c40cf92367 100644 --- a/helloworld-jms/README.md +++ b/helloworld-jms/README.md @@ -30,12 +30,12 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. 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#addapplicationuser) +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 Enterprise Application Platform 6 server @@ -164,13 +164,13 @@ The example provides for a certain amount of customization for the `mvn:exec` pl * `username` - This username is used for both the JMS connection and the JNDI look-up. Instructions to set up the quickstart application user can be found here: [Add an Application User](../README.md#addapplicationuser). + This username is used for both the JMS connection and the JNDI look-up. Instructions to set up the quickstart application user can be found here: [Add an Application User](../README.md#add-an-application-user). Default: `quickstartUser` * `password` - This password is used for both the JMS connection and the JNDI look-up. Instructions to set up the quickstart application user can be found here: [Add an Application User](../README.md#addapplicationuser) + This password is used for both the JMS connection and the JNDI look-up. Instructions to set up the quickstart application user can be found here: [Add an Application User](../README.md#add-an-application-user) Default: `quickstartPwd1!` @@ -243,7 +243,7 @@ This script removes the `test` queue from the `messaging` subsystem in the serve Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/helloworld-mdb/README.md b/helloworld-mdb/README.md index 84b41d76cb..b147f1f099 100644 --- a/helloworld-mdb/README.md +++ b/helloworld-mdb/README.md @@ -29,7 +29,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Full Profile @@ -45,7 +45,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Full Profil 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -93,7 +93,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/helloworld-osgi/README.md b/helloworld-osgi/README.md index 89fb70e2c6..5e63818116 100644 --- a/helloworld-osgi/README.md +++ b/helloworld-osgi/README.md @@ -26,7 +26,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -49,7 +49,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -80,7 +80,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/helloworld-rf/README.md b/helloworld-rf/README.md index e5b91ef82b..802e29daa4 100644 --- a/helloworld-rf/README.md +++ b/helloworld-rf/README.md @@ -26,7 +26,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -42,7 +42,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -71,7 +71,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/helloworld-rs/README.md b/helloworld-rs/README.md index b68dcf4d92..3e3284ad25 100644 --- a/helloworld-rs/README.md +++ b/helloworld-rs/README.md @@ -24,7 +24,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -40,7 +40,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -73,7 +73,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application @@ -85,7 +85,6 @@ If you want to debug the source code or look at the Javadocs of any library in t mvn dependency:resolve -Dclassifier=javadoc - Build and Deploy the Quickstart - to OpenShift ------------------------- diff --git a/helloworld-singleton/README.md b/helloworld-singleton/README.md index 341f1b0f1f..11371cf13c 100644 --- a/helloworld-singleton/README.md +++ b/helloworld-singleton/README.md @@ -23,7 +23,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -39,7 +39,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -74,7 +74,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/helloworld-ws/README.md b/helloworld-ws/README.md index e595eaebe9..cf8d91570d 100644 --- a/helloworld-ws/README.md +++ b/helloworld-ws/README.md @@ -23,7 +23,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Custom Options @@ -39,7 +39,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Custom Opti 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -70,7 +70,7 @@ Run the Client Tests using Arquillian This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container. -_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#arquilliantests) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -96,7 +96,7 @@ The following expected output should appear. The output shows what was said to t Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/helloworld/README.md b/helloworld/README.md index 07ba0342b9..dad60d9d4b 100644 --- a/helloworld/README.md +++ b/helloworld/README.md @@ -25,7 +25,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -41,7 +41,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -70,7 +70,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/hibernate3/README.md b/hibernate3/README.md index 0d2932e19d..a57a297d53 100644 --- a/hibernate3/README.md +++ b/hibernate3/README.md @@ -32,7 +32,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -48,7 +48,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -76,7 +76,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/hibernate4/README.md b/hibernate4/README.md index f2a17d1153..5dd123d1fa 100644 --- a/hibernate4/README.md +++ b/hibernate4/README.md @@ -28,7 +28,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Add the Correct Dependencies @@ -72,7 +72,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -101,7 +101,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/hotrod-endpoint/README.md b/hotrod-endpoint/README.md index 3e017c7eee..8836910cb9 100644 --- a/hotrod-endpoint/README.md +++ b/hotrod-endpoint/README.md @@ -26,7 +26,7 @@ The application this project produces is designed to be run on JBoss Data Grid 6 Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#configure-maven-) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Configure JDG @@ -34,7 +34,7 @@ Configure JDG 1. Obtain JDG server distribution on Red Hat's Customer Portal at https://access.redhat.com/jbossnetwork/restricted/listSoftware.html -2. Install a JDBC driver into JDG (since JDG includes H2 by default, this step may be skipped for the scope of this example). More information can be found at https://access.redhat.com/knowledge/docs/en-US/JBoss_Enterprise_Application_Platform/6/html/Administration_and_Configuration_Guide/chap-Datasource_Management.html . _NOTE: JDG does not support deploying applications so one cannot install it as a deployment._ +2. Install a JDBC driver into JDG (since JDG includes H2 by default, this step may be skipped for the scope of this example). More information can be found in the DataSource Management chapter of the Administration and Configuration Guide for JBoss Enterprise Application Platform on the Customer Portal at . _NOTE: JDG does not support deploying applications so one cannot install it as a deployment._ 3. This Quickstart uses JDBC to store the cache. To permit this, it's necessary to alter JDG configuration file (`JDG_HOME/standalone/configuration/standalone.xml`) to contain the following definitions: @@ -127,7 +127,7 @@ Start JBoss Data Grid 6 Build and Run 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. diff --git a/inter-app/README.md b/inter-app/README.md index 1734462035..d6eff570ff 100644 --- a/inter-app/README.md +++ b/inter-app/README.md @@ -32,7 +32,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 ------------------------- @@ -47,7 +47,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -80,7 +80,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application ------------------------------------ diff --git a/jax-rs-client/README.md b/jax-rs-client/README.md index 7e7a96289f..a3bb9cfe66 100644 --- a/jax-rs-client/README.md +++ b/jax-rs-client/README.md @@ -28,7 +28,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Prerequisites @@ -48,7 +48,7 @@ Run the Arquillian Tests This quickstart provides Arquillian tests. -_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._ +_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. 2. Make sure the `helloworld-rs` quickstart has been deployed on the server as noted in the **Prerequisites** section above. @@ -64,24 +64,23 @@ Investigate the Console Output This command will compile the example and execute a test to make two separate requests to the Web Service. Towards the end of the Maven build output, you should see the following if the execution is successful: -=============================================== -URL: http://localhost:8080/jboss-as-helloworld-rs/rest/xml -MediaType: application/xml + =============================================== + URL: http://localhost:8080/jboss-as-helloworld-rs/rest/xml + MediaType: application/xml -*** Response from Server *** + *** Response from Server *** -Hello World! + Hello World! + + =============================================== + =============================================== + URL: http://localhost:8080/jboss-as-helloworld-rs/rest/json + MediaType: application/json -=============================================== -=============================================== -URL: http://localhost:8080/jboss-as-helloworld-rs/rest/json -MediaType: application/json + *** Response from Server *** -*** Response from Server *** - -{"result":"Hello World!"} - -=============================================== + {"result":"Hello World!"} + =============================================== OpenShift @@ -93,7 +92,7 @@ To make this quickstart more interesting, deploy the RESTful service to OpenShif Build and Deploy the Quickstart - to OpenShift ------------------------- -_IMPORTANT_: This quickstart depends on the deployment of the `helloworld-rs` quickstart to OpenShift for its test. Follow the instructions [Build and Deploy the Quickstart - to OpenShift](../helloworld-rs/README.md#openShiftInstructions) in the helloworld-rs README to deploy that application to OpenShift. Do NOT yet follow the step "Destroy the OpenShift Application". +_IMPORTANT_: This quickstart depends on the deployment of the `helloworld-rs` quickstart to OpenShift for its test. Follow the instructions [Build and Deploy the Quickstart - to OpenShift](../helloworld-rs/README.md#build-and-deploy-the-quickstart-to-openshift) in the helloworld-rs README to deploy that application to OpenShift. Do NOT yet follow the step "Destroy the OpenShift Application". As it says in the helloworld-rs instructions, you can verify the deployment of the `helloworld-rs` quickstart by accessing the following content. Be sure to replace the `quickstart` in the URL with your domain name. @@ -127,24 +126,24 @@ Type the following command to run the jax-rs-client: This command will compile the example and execute a test to make two separate requests to the Web Service. Towards the end of the Maven build output, you should see the following if the execution is successful: -=============================================== -URL: http://helloworldrs-quickstart.rhcloud.com/rest/xml -MediaType: application/xml + =============================================== + URL: http://helloworldrs-quickstart.rhcloud.com/rest/xml + MediaType: application/xml -*** Response from Server *** + *** Response from Server *** -Hello World! + Hello World! -=============================================== -=============================================== -URL: http://helloworldrs-quickstart.rhcloud.com/rest/json -MediaType: application/json + =============================================== + =============================================== + URL: http://helloworldrs-quickstart.rhcloud.com/rest/json + MediaType: application/json -*** Response from Server *** + *** Response from Server *** -{"result":"Hello World!"} + {"result":"Hello World!"} -=============================================== + =============================================== When you are finished testing, restore the `pom.xml` file to the previous version if you want to test locally. diff --git a/jta-crash-rec/README.md b/jta-crash-rec/README.md index 6ea8bdf219..49171773f6 100644 --- a/jta-crash-rec/README.md +++ b/jta-crash-rec/README.md @@ -37,18 +37,16 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Download and Configure Byteman ------------------------ -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#byteman). +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). - - Clear the Transaction ObjectStore ------------------------- @@ -66,13 +64,13 @@ Make sure there is no transaction objectstore data left after testing this or an Configure the JBoss server --------------------------- -If you have run the `jts` or `jts-distributed-crash-recovery` quickstarts, make sure you followed the instructions to [Remove the JTS Configuration from the JBoss server](../jts/README.md#remove-jts-configuration). The Byteman script will only run in JTA mode. It will not not run in JTS mode and you will not be able to simulate the server crash. +If you have run the `jts` or `jts-distributed-crash-recovery` quickstarts, make sure you followed the instructions to [Remove the JTS Configuration from the JBoss server](../jts/README.md#remove-the-jts-configuration-from-the-jboss-server). The Byteman script will only run in JTA mode. It will not not run in JTS mode and you will not be able to simulate the server crash. - +Start the JBoss Server +--------------- Start JBoss Enterprise Application Platform 6 or JBoss AS 7 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 server with the full profile: @@ -81,11 +79,10 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Full Profil For Windows: JBOSS_HOME\bin\standalone.bat -c standalone-full.xml - 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -96,7 +93,6 @@ _NOTE: The following build command assumes you have configured your Maven user s 4. This will deploy `target/jboss-as-jta-crash-rec.war` to the running instance of the server. - Access the application --------------------- @@ -117,12 +113,12 @@ Test the application 4. To demonstrate XA recovery, you need to enable the Byteman tool to terminate the application server while _phase 2_ is running as follows: * Stop the JBoss server. - * [Clear any transaction objectstore data](#clear-transaction-objectstore) remaining from previous tests. - * Follow the instructions to [halt the application using Byteman](../README.md#byteman-halt). The following text will be appended to the server configuration file: + * [Clear the transaction objectstore data](#clear-the-transaction-objectstore) remaining from previous tests. + * Follow the instructions to [halt the application using Byteman](../README.md#halt-the-application-using-byteman). The following text will be appended to the server configuration file: For Linux: JAVA_OPTS="-javaagent:/PATH_TO_BYTEMAN_DOWNLOAD/lib/byteman.jar=script:/PATH_TO_QUICKSTARTS/jta-crash-rec/src/main/scripts/xa.btm ${JAVA_OPTS}" For Windows: JAVA_OPTS=%JAVA_OPTS% -javaagent:C:PATH_TO_BYTEMAN_DOWNLOAD\lib\byteman.jar=script:C:\PATH_TO_QUICKSTARTS\jta-crash-rec\src\main\scripts\xa.btm %JAVA_OPTS% - * [Start the JBoss server](#startserver) as instructed above. + * [Start the JBoss server](#start-the-jboss-server) as instructed above. 5. Once you complete step 4, you are ready to create a _recovery record_. Go to the application URL and insert another row into the database. At this point, Byteman halts the application server. @@ -157,8 +153,8 @@ Test the application * Stop the H2 console to close the database connections. Otherwise, you may see messages like the following when you start your server: `Database may be already in use: "Locked by another process"` - * [Disable the Byteman script](../README.md#byteman-disable) by restoring the backup server configuration file. - * [Start the JBoss server](#startserver) as instructed above. + * [Disable the Byteman script](../README.md#disable-the-byteman-script) by restoring the backup server configuration file. + * [Start the JBoss server](#start-the-jboss-server) as instructed above. * Load the web interface to the application * By the time the JBoss server is ready, the transaction should have recovered. * A message is printed on the JBoss server console when the consumer has completed the update. Look for a line that reads 'JTA Crash Record Quickstart: key value pair updated via JMS'. @@ -182,7 +178,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application ------------------------------------ diff --git a/jts-distributed-crash-rec/README.md b/jts-distributed-crash-rec/README.md index 0b070b6452..a981a1e025 100644 --- a/jts-distributed-crash-rec/README.md +++ b/jts-distributed-crash-rec/README.md @@ -40,13 +40,13 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Configure Byteman ----------------- -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#byteman) +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) Prerequisites @@ -62,8 +62,6 @@ IMPORTANT: This quickstart depends on the deployment of the `jts` quickstart for You can verify the deployment of the `jts` quickstart by accessing the following URL: . - - Clear the Transaction ObjectStore ------------------------- @@ -81,12 +79,12 @@ Make sure there is no transaction objectstore data left after testing this or an Test the Application ----------------------------------- -1. If you have not yet done so, configure the two application servers and deploy the `jts` quickstart. Follow the instructions in the `jts` [README](../jts/README.md) file. +1. If you have not yet done so, configure the two application servers and deploy the `jts` quickstart. Follow the instructions in the [jts README](../jts/README.md) file. 2. Configure Byteman to halt JBoss server 1 * Stop the JBoss servers. - * [Clear any transaction objectstore data](#clear-transaction-objectstore) remaining from previous tests. - * Follow the instructions to [halt application server 1 using Byteman](../README.md#byteman-halt). The following 2 lines of text will be appended to the server configuration file for server 1 only: + * [Clear the transaction objectstore data](#clear-the-transaction-objectstore) remaining from previous tests. + * Follow the instructions to [halt application server 1 using Byteman](../README.md#halt-the-application-using-byteman). The following 2 lines of text will be appended to the server configuration file for server 1 only: For Linux: JAVA_OPTS="-javaagent:/PATH_TO_BYTEMAN_DOWNLOAD/lib/byteman.jar=script:/PATH_TO_QUICKSTARTS/jts-distributed-crash-rec/byteman-scripts/failAfterPrepare.btm ${JAVA_OPTS}" @@ -173,7 +171,7 @@ Test the Application `-- 0_ffffc0a8013c_-2eb1158b_4f280ce3_1a -6. [Disable the Byteman script](../README.md#byteman-disable) by restoring the backup configuration file for server 1. +6. [Disable the Byteman script](../README.md#disable-the-byteman-script) by restoring the backup configuration file for server 1. 7. Follow the steps above to restart server 1 and wait for recovery to complete. @@ -268,4 +266,4 @@ Test the Application 7. After recovery is complete, access the application URL . The user you created should now appear in the list. -8. Do NOT forget to [disable the Byteman script](../README.md#byteman-disable) by restoring the backup server configuration file. The Byteman rule must be removed to ensure that your application server will be able to commit 2PC transactions! +8. Do NOT forget to [disable the Byteman script](../README.md#disable-the-byteman-script) by restoring the backup server configuration file. The Byteman rule must be removed to ensure that your application server will be able to commit 2PC transactions! diff --git a/jts/README.md b/jts/README.md index f229ae4ef4..4d6a66028e 100755 --- a/jts/README.md +++ b/jts/README.md @@ -52,7 +52,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Prerequisites @@ -66,7 +66,7 @@ This quickstart requires the configuration of two servers. The first server must Install the PostgreSQL Database ------------------------------- -This quickstart requires the PostgreSQL database. Instructions to install an configure PostgreSQL can be found here: [Install and Configure the PostgreSQL Database](../README.md#postgresql) +This quickstart requires the PostgreSQL database. Instructions to install an configure PostgreSQL can be found here: [Install and Configure the PostgreSQL Database](../README.md#install-and-configure-the-postgresql-database) _Note_: For the purpose of this quickstart, replace the word QUICKSTART_DATABASENAME with `jts-quickstart-database` in the PostgreSQL instructions. @@ -129,7 +129,7 @@ This script configures the server to use jts transaction processing. You should /subsystem=transactions/:write-attribute(name=jts,value=true) /subsystem=transactions/:write-attribute(name=node-identifier,value=${jboss.tx.node.id}) -4. _NOTE:_ When you have completed testing this quickstart, it is important to [Remove the JTS Configuration from the JBoss Server](#remove-jts-configuration). +4. _NOTE:_ When you have completed testing this quickstart, it is important to [Remove the JTS Configuration from the JBoss Server](#remove-the-jts-configuration-from-the-jboss-server). #### Modify the Server Configuration Manually @@ -156,7 +156,7 @@ This script configures the server to use jts transaction processing. You should -4. _NOTE:_ When you have completed testing this quickstart, it is important to [Remove the JTS Configuration from the JBoss Server](#remove-jts-configuration). +4. _NOTE:_ When you have completed testing this quickstart, it is important to [Remove the JTS Configuration from the JBoss Server](#remove-the-jts-configuration-from-the-jboss-server). ### Clone the JBOSS_HOME Directory @@ -164,10 +164,10 @@ Make a copy of this JBoss directory structure to use for the second server. ### Configure Server1 to use PostgreSQL -2. Application server 1 must be configured to use PostgreSQL as per the instructions in [Install and Configure the PostgreSQL Database] (../README.md#postgresql). +2. Application server 1 must be configured to use PostgreSQL as per the instructions in [Install and Configure the PostgreSQL Database] (../README.md#install-and-configure-the-postgresql-database). * Be sure to start the PostgreSQL database. - * [Add the PostgreSQL Module](../README.md#addpostgresqlmodule) to the Application 1 server `modules/` directory. - * [Add the PostgreSQL driver](../README.md#addpostgresqldriver) to the Application 1 server configuration file. + * [Add the PostgreSQL Module](../README.md#add-the-postgresql-module-to-the-jboss-server) to the Application 1 server `modules/` directory. + * [Add the PostgreSQL driver](../README.md#add-the-postgresql-driver-configuration-to-the-jboss-server) to the Application 1 server configuration file. Start the JBoss Enterprise Application Platform 6 or JBoss AS 7 Servers @@ -230,7 +230,6 @@ Undeploy the Archive mvn package jboss-as:undeploy - Remove the JTS Configuration from the JBoss Server --------------------------- diff --git a/kitchensink-angularjs/README.md b/kitchensink-angularjs/README.md index 63ee4d952e..248c3d0466 100644 --- a/kitchensink-angularjs/README.md +++ b/kitchensink-angularjs/README.md @@ -25,7 +25,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -41,7 +41,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -73,7 +73,7 @@ Run the Arquillian Tests This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container. -_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#arquilliantests) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -84,7 +84,7 @@ _NOTE: The following commands assume you have configured your Maven user setting Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/kitchensink-backbone/README.md b/kitchensink-backbone/README.md index 1f990162ef..0aedbff6bb 100644 --- a/kitchensink-backbone/README.md +++ b/kitchensink-backbone/README.md @@ -35,7 +35,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -52,7 +52,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#buildanddeploy) for +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. @@ -87,7 +87,7 @@ This quickstart provides Arquillian tests. By default, these tests are configure require the use of a container. _NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include -Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#arquilliantests) for complete +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. @@ -100,7 +100,7 @@ instructions and additional options._ Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see -[Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +[Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/kitchensink-cordova/README.md b/kitchensink-cordova/README.md index d920cf73b2..be3eac494f 100644 --- a/kitchensink-cordova/README.md +++ b/kitchensink-cordova/README.md @@ -9,9 +9,9 @@ Target Product: WFK What is it? ----------- -This project serves as an example of the HTML5 [kitchensink quickstart](https://github.com/jboss-jdf/jboss-as-quickstart/tree/master/kitchensink-html5-mobile), converted to an [Apache Cordova](http://incubator.apache.org/cordova/) based, hybrid application. +This project serves as an example of the HTML5 [kitchensink quickstart](https://github.com/jboss-jdf/jboss-as-quickstart/tree/master/kitchensink-html5-mobile), converted to an [Apache Cordova](http://cordova.apache.org/) based, hybrid application. -What does all of that mean? Basically, this takes our [HTML5 + REST](https://community.jboss.org/docs/DOC-17326) / [jQuery Mobile](http://www.jquerymobile.com) based web app and converts it to a native app for both iOS and Android. Currently, these apps will need to be built separately but in the future we hope to provide a single build step for all supported mobile OS types. These concepts can be applied to the conversion of most HTML5/JS based web apps by just replacing the specific paths described in this article with paths that match your environment. +What does all of that mean? Basically, this takes our [HTML5 + REST](https://community.jboss.org/wiki/HTML5RESTApplications) / [jQuery Mobile](http://jquerymobile.com/) based web app and converts it to a native app for both iOS and Android. Currently, these apps will need to be built separately but in the future we hope to provide a single build step for all supported mobile OS types. These concepts can be applied to the conversion of most HTML5/JS based web apps by just replacing the specific paths described in this article with paths that match your environment. Available Hybrid Applications ----------------------------- diff --git a/kitchensink-cordova/android/README.md b/kitchensink-cordova/android/README.md index 7b7f5172c2..4b12ce2ab0 100644 --- a/kitchensink-cordova/android/README.md +++ b/kitchensink-cordova/android/README.md @@ -67,7 +67,7 @@ The application will be running on the Emulator. Converting a HTML5 + REST Web App to a Hybrid App with Apache Cordova -------------------------------------------------------------------------------- -If you have an existing Web Application based on HTML5 + REST you can follow [this guide](http://aerogear.org/docs/guides/HTML5ToHybridWithCordova) +If you have an existing Web Application based on HTML5 + REST you can follow [this guide](http://aerogear.org/docs/guides/HTML5ToHybridWithCordova/) diff --git a/kitchensink-cordova/ios/README.md b/kitchensink-cordova/ios/README.md index 07d7bbf712..e2c21e3469 100644 --- a/kitchensink-cordova/ios/README.md +++ b/kitchensink-cordova/ios/README.md @@ -43,7 +43,7 @@ If the toolbar in XCode is visible, click on the *Run* button. This will start t Converting a HTML5 + REST Web App to a Hybrid App with Apache Cordova -------------------------------------------------------------------------------- -If you have an existing Web Application based on HTML5 + REST you can follow [this guide](http://aerogear.org/docs/guides/HTML5ToHybridWithCordova) +If you have an existing Web Application based on HTML5 + REST you can follow [this guide](http://aerogear.org/docs/guides/HTML5ToHybridWithCordova/) diff --git a/kitchensink-deltaspike/README.md b/kitchensink-deltaspike/README.md index 2fb740a6d8..e641a7b93e 100644 --- a/kitchensink-deltaspike/README.md +++ b/kitchensink-deltaspike/README.md @@ -41,7 +41,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -57,7 +57,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -89,7 +89,7 @@ Run the Arquillian Tests This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container. -_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#arquilliantests) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -103,7 +103,7 @@ _NOTE: If you use the Maven settings command line argument with this quickstart, Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/kitchensink-ear/README.md b/kitchensink-ear/README.md index d591a2a82e..2abd36ca5c 100644 --- a/kitchensink-ear/README.md +++ b/kitchensink-ear/README.md @@ -25,7 +25,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -41,7 +41,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -80,7 +80,7 @@ Run the Arquillian Tests This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container. -_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#arquilliantests) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -115,7 +115,7 @@ You should see messages similar to the following: Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/kitchensink-html5-mobile/README.md b/kitchensink-html5-mobile/README.md index 2a51a276c0..50bba02225 100644 --- a/kitchensink-html5-mobile/README.md +++ b/kitchensink-html5-mobile/README.md @@ -62,7 +62,7 @@ To undeploy run this command: mvn jboss-as:undeploy -You can also start the JBoss container and deploy the project using JBoss Tools. See the Getting Started Developing Applications Guide for more information. +You can also start the JBoss container and deploy the project using JBoss Tools. See the [Get Started Developing Applications](http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/guide/Introduction/ "Get Started Developing Applications") for more information. ### Deploying to OpenShift @@ -112,7 +112,7 @@ Importing the project into an IDE If you created the project using the Maven archetype wizard in your IDE (Eclipse, NetBeans or IntelliJ IDEA), then there is nothing to do. You should already have an IDE project. -Detailed instructions for using Eclipse / JBoss Tools with are provided in the Getting Started Developing Applications Guide. +Detailed instructions for using Eclipse / JBoss Tools with are provided in the [Get Started Developing Applications](http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/guide/Introduction/ "Get Started Developing Applications"). If you created the project from the command line using archetype:generate, then you need to import the project into your IDE. If you are using NetBeans 6.8 or IntelliJ IDEA 9, then all you have to do is open the project as an existing project. Both of these IDEs recognize Maven projects natively. diff --git a/kitchensink-jsp/README.md b/kitchensink-jsp/README.md index 87c003af29..d91749444f 100644 --- a/kitchensink-jsp/README.md +++ b/kitchensink-jsp/README.md @@ -27,7 +27,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -43,7 +43,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -74,7 +74,7 @@ Run the Arquillian Tests This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container. -_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#arquilliantests) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -85,7 +85,7 @@ _NOTE: The following commands assume you have configured your Maven user setting Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/kitchensink-ml-ear/README.md b/kitchensink-ml-ear/README.md index a6d2623dfc..505d52069b 100644 --- a/kitchensink-ml-ear/README.md +++ b/kitchensink-ml-ear/README.md @@ -102,7 +102,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -118,7 +118,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -157,7 +157,7 @@ Run the Arquillian Tests This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container. -_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#arquilliantests) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -192,7 +192,7 @@ You should see messages similar to the following: Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/kitchensink-ml/README.md b/kitchensink-ml/README.md index 3d1431b763..3ccae6cadf 100644 --- a/kitchensink-ml/README.md +++ b/kitchensink-ml/README.md @@ -103,7 +103,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -119,7 +119,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -152,7 +152,7 @@ Run the Arquillian Tests This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container. -_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#arquilliantests) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -163,7 +163,7 @@ _NOTE: The following commands assume you have configured your Maven user setting Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/kitchensink-rf/README.md b/kitchensink-rf/README.md index b24286eac4..1bece6cd89 100644 --- a/kitchensink-rf/README.md +++ b/kitchensink-rf/README.md @@ -41,7 +41,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -57,7 +57,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -89,7 +89,7 @@ Run the Arquillian Tests This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container. -_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#arquilliantests) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -100,7 +100,7 @@ _NOTE: The following commands assume you have configured your Maven user setting Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/kitchensink-spring/README.md b/kitchensink-spring/README.md index 88d87c8f66..eaa0e1d9f4 100644 --- a/kitchensink-spring/README.md +++ b/kitchensink-spring/README.md @@ -22,11 +22,11 @@ The basic version showcases the above technologies without any extra features, w _NOTE: The following describes the 5 quickstart provided in this example. Many of the following use cases are contrived, but the purpose of the additional quickstarts is to showcase Spring 3.2's outstanding new features._ -* `basic` - This quickstart showcases the above technologies without any extra features. For more information about the basic quickstart, see the basic [README]() file. -* `asyncrequestmapping` - This quickstart showcases Spring 3.2's Asynchronous Callable Function [More on Spring's Asynchronous Request Processing](). For more information about the asyncrequestmapping quickstart, see the asyncrequestmapping [README]() file. -* `controlleradvice` - This quickstarts showcases Spring 3.2's new `@ControllerAdvice` which allows the user to configure various aspects such as global exception handler, init binders, and adding global model atrributes. For more information about the controlleradvice quickstart, see the controlleradvice [README]() file. -* `matrixvariables` - This quickstarts showcases Spring 3.2's added support for Matrix Variables in urls, e.g. http://localhost:8080/something;p=2;q=3. In this quickstart the matrix variables are used for filtering purposes. For more information about the matrixvariables quickstart, see the matrixvariables [README]() file. -* `springmvctest` - This quickstart adds `MemberMockMVCTest.java` to showcase a use case of `MockMVC` and `RestTemplate` to test the mvc aspect of the application which was previously not possible without external tools such as Arquillian. For more information about the springmvctest quickstart, see the springmvctest [README]() file. +* `basic` - This quickstart showcases the above technologies without any extra features. For more information about the basic quickstart, see the [basic README](basic/README.md) file. +* `asyncrequestmapping` - This quickstart showcases Spring 3.2's Asynchronous Callable Function [More on Spring's Asynchronous Request Processing](). For more information about the asyncrequestmapping quickstart, see the [asyncrequestmapping README](asyncrequestmapping/README.md) file. +* `controlleradvice` - This quickstarts showcases Spring 3.2's new `@ControllerAdvice` which allows the user to configure various aspects such as global exception handler, init binders, and adding global model atrributes. For more information about the controlleradvice quickstart, see the [controlleradvice README](controlleradvice/README.md) file. +* `matrixvariables` - This quickstarts showcases Spring 3.2's added support for Matrix Variables in urls, e.g. http://localhost:8080/something;p=2;q=3. In this quickstart the matrix variables are used for filtering purposes. For more information about the matrixvariables quickstart, see the [matrixvariables README](matrixvariables/README.md) file. +* `springmvctest` - This quickstart adds `MemberMockMVCTest.java` to showcase a use case of `MockMVC` and `RestTemplate` to test the mvc aspect of the application which was previously not possible without external tools such as Arquillian. For more information about the springmvctest quickstart, see the [springmvctest README](springmvctest/README.md) file. System requirements ------------------- @@ -51,7 +51,7 @@ Build and Deploy the Quickstart _NOTE: The following applies to each of the quickstarts in this project. `QUICKSTART_NAME` should be replaced by the respective quickstart that you are working with._ -_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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -88,7 +88,7 @@ Or you can manually remove the application by removing `jboss-as-kitchensink-spr Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/kitchensink-spring/asyncrequestmapping/README.md b/kitchensink-spring/asyncrequestmapping/README.md index d7638959c3..5142fc1144 100644 --- a/kitchensink-spring/asyncrequestmapping/README.md +++ b/kitchensink-spring/asyncrequestmapping/README.md @@ -37,7 +37,7 @@ Configure Maven 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -68,7 +68,7 @@ Or you can manually remove the application by removing jboss-as-kitchensink-spri Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/kitchensink-spring/basic/README.md b/kitchensink-spring/basic/README.md index ac62f92261..9bb5218c56 100644 --- a/kitchensink-spring/basic/README.md +++ b/kitchensink-spring/basic/README.md @@ -44,7 +44,7 @@ Configure Maven 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -75,7 +75,7 @@ Or you can manually remove the application by removing jboss-as-kitchensink-spri Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/kitchensink-spring/controlleradvice/README.md b/kitchensink-spring/controlleradvice/README.md index c011ca6ef1..6a75209cf1 100644 --- a/kitchensink-spring/controlleradvice/README.md +++ b/kitchensink-spring/controlleradvice/README.md @@ -39,7 +39,7 @@ Configure Maven 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -70,7 +70,7 @@ Or you can manually remove the application by removing jboss-as-kitchensink-spri Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/kitchensink-spring/matrixvariables/README.md b/kitchensink-spring/matrixvariables/README.md index 6f8ac2021e..3eef24b2a0 100644 --- a/kitchensink-spring/matrixvariables/README.md +++ b/kitchensink-spring/matrixvariables/README.md @@ -41,7 +41,7 @@ Configure Maven 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -72,7 +72,7 @@ Or you can manually remove the application by removing jboss-as-kitchensink-spri Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/kitchensink-spring/springmvctest/README.md b/kitchensink-spring/springmvctest/README.md index 7afd706fe1..8bbae45564 100644 --- a/kitchensink-spring/springmvctest/README.md +++ b/kitchensink-spring/springmvctest/README.md @@ -39,7 +39,7 @@ Configure Maven 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -70,7 +70,7 @@ Or you can manually remove the application by removing jboss-as-kitchensink-spri Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/kitchensink/README.md b/kitchensink/README.md index ffd5c90ea3..21572a66b1 100644 --- a/kitchensink/README.md +++ b/kitchensink/README.md @@ -27,7 +27,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -43,7 +43,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -75,7 +75,7 @@ Run the Arquillian Tests This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container. -_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#arquilliantests) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -86,7 +86,7 @@ _NOTE: The following commands assume you have configured your Maven user setting Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/log4j/README.md b/log4j/README.md index bc76b11942..3e02ce2467 100644 --- a/log4j/README.md +++ b/log4j/README.md @@ -29,7 +29,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -45,7 +45,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -73,7 +73,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/logging-tools/README.md b/logging-tools/README.md index b8f31d1f40..62a247ff6d 100644 --- a/logging-tools/README.md +++ b/logging-tools/README.md @@ -28,7 +28,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Configure the JBoss Server to Start With a Different Locale (Optional) @@ -62,7 +62,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. @@ -140,7 +140,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/logging/README.md b/logging/README.md index 5800d011ab..06a12e86b0 100644 --- a/logging/README.md +++ b/logging/README.md @@ -29,12 +29,12 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. - -Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile +Start the JBoss Server ------------------------- +Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 1. Open a command line and navigate to the root of the JBoss server directory. 2. The following shows the command line to start the server with the web profile: @@ -43,11 +43,10 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile For Windows: JBOSS_HOME\bin\standalone.bat - Build and Deploy the Quickstart ------------------------- -_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -58,7 +57,6 @@ _NOTE: The following build command assumes you have configured your Maven user s 4. This deploys `target/jboss-as-logging.war` to the running instance of the server. - Access the application --------------------- @@ -329,9 +327,9 @@ You should see the following result when you run the script: ### Restart the Server and Test -1. If your server is not started (i.e. you didn't use one of the CLI routes), then [Start the server](#startserver). -2. [Build and deploy](#buildanddeploy) the quickstart. -3. [Access the application](#accessapp). +1. If your server is not started (i.e. you didn't use one of the CLI routes), then [Start the server](#start-the-jboss-server). +2. [Build and deploy the quickstart](#build-and-deploy-the-quickstart). +3. [Access the application](#access-the-application). Recheck the Server Logs @@ -425,7 +423,7 @@ This script removes the log and file handlers from the `logging` subsystem in th Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/mail/README.md b/mail/README.md index d46533fd9b..941c77bb5d 100644 --- a/mail/README.md +++ b/mail/README.md @@ -44,7 +44,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -60,7 +60,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -89,7 +89,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/memcached-endpoint/README.md b/memcached-endpoint/README.md index e755d0fba6..4f4555e338 100644 --- a/memcached-endpoint/README.md +++ b/memcached-endpoint/README.md @@ -26,7 +26,7 @@ The application this project produces is designed to be run on JBoss Data Grid 6 Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#configure-maven-) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Configure JDG @@ -34,7 +34,7 @@ Configure JDG 1. Obtain JDG server distribution on Red Hat's Customer Portal at https://access.redhat.com/jbossnetwork/restricted/listSoftware.html -2. Install a JDBC driver into JDG (since JDG includes H2 by default, this step may be skipped for the scope of this example). More information can be found at https://access.redhat.com/knowledge/docs/en-US/JBoss_Enterprise_Application_Platform/6/html/Administration_and_Configuration_Guide/chap-Datasource_Management.html . _NOTE: JDG does not support deploying applications so one cannot install it as a deployment._ +2. Install a JDBC driver into JDG (since JDG includes H2 by default, this step may be skipped for the scope of this example). More information can be found in the DataSource Management chapter of the Administration and Configuration Guide for JBoss Enterprise Application Platform on the Customer Portal at . _NOTE: JDG does not support deploying applications so one cannot install it as a deployment._ 3. This Quickstart uses JDBC to store the cache. To permit this, it's necessary to alter JDG configuration file (`JDG_HOME/standalone/configuration/standalone.xml`) to contain the following definitions: @@ -128,7 +128,7 @@ Start JBoss Data Grid 6 Build and Run 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. diff --git a/numberguess/README.md b/numberguess/README.md index bacc370230..8890386592 100644 --- a/numberguess/README.md +++ b/numberguess/README.md @@ -25,7 +25,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -41,7 +41,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -70,7 +70,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/payment-cdi-event/README.md b/payment-cdi-event/README.md index e52f16ab05..e9b53fcda2 100644 --- a/payment-cdi-event/README.md +++ b/payment-cdi-event/README.md @@ -49,7 +49,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -65,7 +65,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -94,7 +94,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/picketlink-authentication-idm-jsf/README.md b/picketlink-authentication-idm-jsf/README.md index e684694c7c..c40a7ca715 100644 --- a/picketlink-authentication-idm-jsf/README.md +++ b/picketlink-authentication-idm-jsf/README.md @@ -23,7 +23,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -39,7 +39,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -68,7 +68,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/picketlink-authentication-jsf/README.md b/picketlink-authentication-jsf/README.md index b31050bceb..3b600ec4c7 100644 --- a/picketlink-authentication-jsf/README.md +++ b/picketlink-authentication-jsf/README.md @@ -23,7 +23,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -39,7 +39,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -68,7 +68,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/picketlink-authorization-idm-jpa/README.md b/picketlink-authorization-idm-jpa/README.md index 488d768286..737f06bc50 100644 --- a/picketlink-authorization-idm-jpa/README.md +++ b/picketlink-authorization-idm-jpa/README.md @@ -23,7 +23,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -39,7 +39,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -68,7 +68,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/picketlink-deltaspike-authorization/README.md b/picketlink-deltaspike-authorization/README.md index 02453d86f3..4f58d1c01e 100644 --- a/picketlink-deltaspike-authorization/README.md +++ b/picketlink-deltaspike-authorization/README.md @@ -33,7 +33,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 @@ -48,7 +48,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -82,7 +82,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application ------------------------------------ diff --git a/rest-endpoint/README.md b/rest-endpoint/README.md index c0041149f7..d9455b8bdd 100644 --- a/rest-endpoint/README.md +++ b/rest-endpoint/README.md @@ -26,7 +26,7 @@ The application this project produces is designed to be run on JBoss Data Grid 6 Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#configure-maven-) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Configure JDG @@ -34,7 +34,7 @@ Configure JDG 1. Obtain JDG server distribution on Red Hat's Customer Portal at https://access.redhat.com/jbossnetwork/restricted/listSoftware.html -2. Install a JDBC driver into JDG (since JDG includes H2 by default, this step may be skipped for the scope of this example). More information can be found at https://access.redhat.com/knowledge/docs/en-US/JBoss_Enterprise_Application_Platform/6/html/Administration_and_Configuration_Guide/chap-Datasource_Management.html . _NOTE: JDG does not support deploying applications so one cannot install it as a deployment._ +2. Install a JDBC driver into JDG (since JDG includes H2 by default, this step may be skipped for the scope of this example). More information can be found in the DataSource Management chapter of the Administration and Configuration Guide for JBoss Enterprise Application Platform on the Customer Portal at . _NOTE: JDG does not support deploying applications so one cannot install it as a deployment._ 3. This Quickstart uses JDBC to store the cache. To permit this, it's necessary to alter JDG configuration file (`JDG_HOME/standalone/configuration/standalone.xml`) to contain the following definitions: @@ -131,7 +131,7 @@ Start JBoss Data Grid 6 Build and Run 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. diff --git a/richfaces-validation/README.md b/richfaces-validation/README.md index 29f478d0a6..fe6344792a 100644 --- a/richfaces-validation/README.md +++ b/richfaces-validation/README.md @@ -45,7 +45,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -61,7 +61,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -99,7 +99,7 @@ Run the Arquillian Tests This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container. -_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#arquilliantests) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -129,7 +129,7 @@ If you are interested in more details, check `target/surefire-reports` directory Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/servlet-async/README.md b/servlet-async/README.md index 5faaf81ec3..2b78549658 100644 --- a/servlet-async/README.md +++ b/servlet-async/README.md @@ -33,7 +33,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -49,7 +49,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -78,7 +78,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/servlet-filterlistener/README.md b/servlet-filterlistener/README.md index b15abdf988..f773174a3b 100644 --- a/servlet-filterlistener/README.md +++ b/servlet-filterlistener/README.md @@ -22,7 +22,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -38,7 +38,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -67,7 +67,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/servlet-security/README.md b/servlet-security/README.md index 43d8f670b0..de438518d0 100644 --- a/servlet-security/README.md +++ b/servlet-security/README.md @@ -45,7 +45,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Add the Application Users @@ -60,7 +60,7 @@ Using the add-user utility script, you must add the following users to the `Appl The first application user has access rights to the application. The second application user is not authorized to access the application. -For an example of how to use the add-user utility, see instructions in the root README file located here: [Add User](../README.md#addapplicationuser). +For an example of how to use the add-user utility, see instructions in the root README file located here: [Add User](../README.md#add-an-application-user). Define a Security Domain Using the Database JAAS Login Module @@ -139,11 +139,10 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile For Windows: JBOSS_HOME\bin\standalone.bat - Build and Deploy the Quickstart ------------------------- -_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -153,7 +152,6 @@ _NOTE: The following build command assumes you have configured your Maven user s 4. This will deploy `target/jboss-as-servlet-security.war` to the running instance of the server. - Access the Application --------------------- @@ -218,7 +216,7 @@ This script removes the `test` queue from the `messaging` subsystem in the serve Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/shopping-cart/README.md b/shopping-cart/README.md index ffd6fa83d6..e55e523f59 100644 --- a/shopping-cart/README.md +++ b/shopping-cart/README.md @@ -33,7 +33,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -149,7 +149,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/shrinkwrap-resolver/README.md b/shrinkwrap-resolver/README.md index aa6d568323..0905d46813 100644 --- a/shrinkwrap-resolver/README.md +++ b/shrinkwrap-resolver/README.md @@ -5,7 +5,7 @@ Level: Intermediate Technologies: CDI, Arquillian, Shrinkwrap Summary: Demonstrate usage of some Shrinkwrap resolver use cases Target Product: WFK -Source: https://github.com/jboss-jdf/jboss-as-quickstart/shrinkwrap-resolver +Source: What is it? @@ -45,7 +45,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 @@ -62,7 +62,7 @@ Run the Arquillian Tests This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container. -_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#arquilliantests) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. diff --git a/tasks-jsf/README.md b/tasks-jsf/README.md index 45f039f442..e9907dacb5 100644 --- a/tasks-jsf/README.md +++ b/tasks-jsf/README.md @@ -34,7 +34,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven ------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -50,7 +50,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -82,7 +82,7 @@ Run the Arquillian Tests This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container. -_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#arquilliantests) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -93,7 +93,7 @@ _NOTE: The following commands assume you have configured your Maven user setting Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/tasks-rs/README.md b/tasks-rs/README.md index 438567cc38..4908fc3259 100644 --- a/tasks-rs/README.md +++ b/tasks-rs/README.md @@ -31,14 +31,14 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven ------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Add an Application User --------------- -This quickstart uses a secured management interface and requires that you create an application user to access the running application. Instructions to set up an Application user can be found here: [Add an Application User](../README.md#addapplicationuser). After following these instructions. you should have created a user called `quickstartUser` with password `quickstartPwd1!`, belonging to the `guest` role. +This quickstart uses a secured management interface and requires that you create an application user to access the running application. Instructions to set up an Application user can be found here: [Add an Application User](../README.md#add-an-application-user). After following these instructions. you should have created a user called `quickstartUser` with password `quickstartPwd1!`, belonging to the `guest` role. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -54,7 +54,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -75,7 +75,6 @@ Application resources for this quickstart are prefixed with the URL http://local Below you will find instructions to create, display, and delete tasks. - ### Create a Task To associate a task called `task1` with the user `quickstartUser`, you must authenticate as user `quickstartUser` and send an HTTP *POST* request to the url 'http://localhost:8080/jboss-as-tasks-rs/tasks/task1'. @@ -226,7 +225,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/tasks/README.md b/tasks/README.md index 1071c2b8a7..d0f75fd2ae 100644 --- a/tasks/README.md +++ b/tasks/README.md @@ -28,7 +28,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -46,7 +46,7 @@ Run the Arquillian Tests This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container. -_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#arquilliantests) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -108,7 +108,7 @@ Generating ID for a new entity and inserting the entity into the database: Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/temperature-converter/README.md b/temperature-converter/README.md index 4e6105c43a..3426aa5097 100644 --- a/temperature-converter/README.md +++ b/temperature-converter/README.md @@ -33,7 +33,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -49,7 +49,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -85,7 +85,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md/#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/template/README.md b/template/README.md index 73e813143f..4b51f98767 100644 --- a/template/README.md +++ b/template/README.md @@ -41,7 +41,7 @@ Configure Maven Contributor: You can copy or link to the Maven configuration information in the README file in the root folder of the quickstarts. For example: -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Configure Optional Components @@ -51,13 +51,13 @@ Contributor: If your quickstart requires any additional components, decribe how * This quickstart uses a secured management interface and requires that you create a management (or application) user to access the running application. Instructions to set up a Management (or Application) user can be found here: - * [Add a Management User](../README.md#addmanagementuser) + * [Add a Management User](../README.md#add-a-management-user) - * [Add an Application User](../README.md#addapplicationuser) + * [Add an Application User](../README.md#add-an-application-user) - * This quickstart requires the PostgreSQL database. Instructions to install an configure PostgreSQL can be found here: [Install and Configure the PostgreSQL Database](../README.md#postgresql) + * This quickstart requires the PostgreSQL database. Instructions to install an configure PostgreSQL can be found here: [Install and Configure the PostgreSQL Database](../README.md#install-and-configure-the-postgresql-database) - * 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#byteman) + * 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 JBoss Enterprise Application Platform 6 or JBoss AS 7 @@ -81,7 +81,7 @@ Build and Deploy the Quickstart Contributor: If the quickstart is built and deployed using the standard Maven commands, "mvn clean package" and "mvn jboss-as:deploy", copy the following: -_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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -134,7 +134,7 @@ Contributor: For example: This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container. -_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#arquilliantests) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -154,7 +154,7 @@ Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- Contributor: For example: -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application ------------------------------------ diff --git a/wicket-ear/README.md b/wicket-ear/README.md index 1529d219a6..e6a7e75d95 100644 --- a/wicket-ear/README.md +++ b/wicket-ear/README.md @@ -37,7 +37,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -53,7 +53,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -85,7 +85,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/wicket-war/README.md b/wicket-war/README.md index 10d7b7fdb3..b99b608170 100644 --- a/wicket-war/README.md +++ b/wicket-war/README.md @@ -32,7 +32,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -49,7 +49,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. diff --git a/wsat-simple/README.md b/wsat-simple/README.md index 1b5ef13ee0..adec6bcd07 100644 --- a/wsat-simple/README.md +++ b/wsat-simple/README.md @@ -52,7 +52,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Custom Options @@ -76,7 +76,7 @@ Run the Arquillian Tests This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container. -_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#arquilliantests) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -124,7 +124,7 @@ Test rollback: Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application @@ -141,7 +141,7 @@ Build and Deploy the Quickstart - to OpenShift ### Create an OpenShift Express Account and Domain -If you do not yet have an OpenShift account and domain, [Sign in to OpenShift](https://openshift.redhat.com/app/login) to create the account and domain. [Get Started with OpenShift](https://openshift.redhat.com/app/getting_started) will show you how to install the OpenShift Express command line interface. +If you do not yet have an OpenShift account and domain, [Sign in to OpenShift](https://openshift.redhat.com/app/login) to create the account and domain. [Get Started with OpenShift](https://www.openshift.com/get-started) will show you how to install the OpenShift Express command line interface. ### Create the OpenShift Application Note that we use the `jboss-as-quickstart@jboss.org` user for these examples. You need to substitute it with your own user name. diff --git a/wsba-coordinator-completion-simple/README.md b/wsba-coordinator-completion-simple/README.md index 7d90e554f2..65a9096396 100644 --- a/wsba-coordinator-completion-simple/README.md +++ b/wsba-coordinator-completion-simple/README.md @@ -54,7 +54,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Custom Options @@ -74,7 +74,7 @@ Run the Arquillian Tests This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container. -_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#arquilliantests) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -129,7 +129,7 @@ Test cancel: Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/wsba-participant-completion-simple/README.md b/wsba-participant-completion-simple/README.md index ecc92431ac..0c915cda07 100644 --- a/wsba-participant-completion-simple/README.md +++ b/wsba-participant-completion-simple/README.md @@ -59,7 +59,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Custom Options @@ -79,7 +79,7 @@ Run the Arquillian Tests This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container. -_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](../README.md#arquilliantests) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -128,7 +128,7 @@ Test cancel: Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/xml-dom4j/README.md b/xml-dom4j/README.md index 92798dbc3d..af40ce964d 100644 --- a/xml-dom4j/README.md +++ b/xml-dom4j/README.md @@ -25,7 +25,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -41,7 +41,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -70,7 +70,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application diff --git a/xml-jaxp/README.md b/xml-jaxp/README.md index fbbd9ab341..2d2165fdd9 100644 --- a/xml-jaxp/README.md +++ b/xml-jaxp/README.md @@ -25,7 +25,7 @@ The application this project produces is designed to be run on JBoss Enterprise Configure Maven --------------- -If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. +If you have not yet done so, you must [Configure Maven](../README.md#configure-maven) before testing the quickstarts. Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile @@ -41,7 +41,7 @@ Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile 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#buildanddeploy) for complete instructions and additional options._ +_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. 2. Open a command line and navigate to the root directory of this quickstart. @@ -70,7 +70,7 @@ Undeploy the Archive Run the Quickstart in JBoss Developer Studio or Eclipse ------------------------------------- -You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#useeclipse) +You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](../README.md#use-jboss-developer-studio-or-eclipse-to-run-the-quickstarts) Debug the Application