Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

More readme cleanup

  • Loading branch information...
commit 2222919f36d1ac73181fbeb66bf3e718ffe9c482 1 parent 8ddd885
@sgilda sgilda authored
Showing with 135 additions and 137 deletions.
  1. +10 −10 README.md
  2. +3 −3 bean-validation/README.md
  3. +2 −2 bmt/README.md
  4. +3 −3 cdi-injection/README.md
  5. +5 −5 cmt/README.md
  6. +4 −4 ejb-in-ear/README.md
  7. +4 −4 ejb-in-war/README.md
  8. +3 −3 ejb-remote/README.md
  9. +9 −9 ejb-security/README.md
  10. +2 −2 forge-from-scratch/README.md
  11. +2 −2 greeter/README.md
  12. +0 −6 h2-console/README.md
  13. +2 −2 helloworld-errai/README.md
  14. +2 −2 helloworld-gwt/README.md
  15. +2 −2 helloworld-jms/README.md
  16. +2 −2 helloworld-jsf/README.md
  17. +2 −2 helloworld-mdb/README.md
  18. +2 −2 helloworld-osgi/README.md
  19. +5 −5 helloworld-rs/README.md
  20. +2 −2 helloworld-singleton/README.md
  21. +4 −2 helloworld/README.md
  22. +2 −2 hibernate3/README.md
  23. +3 −5 hibernate4/README.md
  24. +1 −1  jts/README.md
  25. +2 −2 kitchensink-ear/README.md
  26. +3 −3 kitchensink-jsp/README.md
  27. +4 −2 kitchensink/README.md
  28. +2 −2 log4j/README.md
  29. +3 −3 mail/README.md
  30. +4 −2 numberguess/README.md
  31. +2 −2 payment-cdi-event/README.md
  32. +2 −2 richfaces-validation/README.md
  33. +2 −2 servlet-async/README.md
  34. +2 −2 servlet-filterlistener/README.md
  35. +9 −8 servlet-security/README.md
  36. +2 −2 shopping-cart/README.md
  37. +2 −2 tasks-jsf/README.md
  38. +4 −5 template/README.md
  39. +2 −2 wicket-ear/README.md
  40. +3 −3 wsat-simple/README.md
  41. +5 −5 wsba-coordinator-completion-simple/README.md
  42. +4 −4 wsba-participant-completion-simple/README.md
  43. +2 −2 xml-jaxp/README.md
View
20 README.md
@@ -170,27 +170,27 @@ The JBoss server can be started a few different ways.
The README for each quickstart will specify which configuration is required to run the example.
<a id="startserverweb"></a>
-#### Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+#### 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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
For Windows: JBOSS_HOME\bin\standalone.bat
<a id="startserverfull"></a>
-#### Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Full Profile
+#### 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 directory.
+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:
For Linux: JBOSS_HOME/bin/standalone.sh -c standalone-full.xml
For Windows: JBOSS_HOME\bin\standalone.bat -c standalone-full.xml
<a id="startservercustom"></a>
-#### Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with Custom Configuration Options
+#### 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 directory.
+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.
For Linux: JBOSS_HOME/bin/standalone.sh CUSTOM_OPTIONS
@@ -294,7 +294,7 @@ The quickstart README should tell you what you should expect to see in the conso
<a id="useeclipse"/>
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 [Boss Enterprise Application Platform 6 Beta](http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/6/html/Beta_Documentation/HOME.html) documentation or the [Getting Started Developing Applications Guide](https://docs.jboss.org/author/display/AS71/Getting+Started+Developing+Applications+Guide "Getting Started Developing Applications Guide").
+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 Beta](http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/6/html/Beta_Documentation/HOME.html) documentation or the [Getting Started Developing Applications Guide](https://docs.jboss.org/author/display/AS71/Getting+Started+Developing+Applications+Guide "Getting Started Developing Applications Guide").
<a id="optionalcomponents"></a>
@@ -332,13 +332,13 @@ The following procedures describe how to add a user with the appropriate permiss
b) Application User (application-users.properties)
(a):
- At the prompt, press enter to take the default Management User
+ At the prompt, press enter to use the default Management User
4. You should see the following response:
Enter the details of the new user to add.
Realm (ManagementRealm) :
- If the quickstart README specifies a realm, type it here. Otherwise, press enter to take the default `ManagementRealm`.
+ If the quickstart README specifies a realm, type it here. Otherwise, press enter to use the default `ManagementRealm`.
5. When prompted, enter the following
Username : admin
@@ -369,7 +369,7 @@ The following procedures describe how to add a user with the appropriate permiss
Enter the details of the new user to add.
Realm (ApplicationRealm) :
- If the quickstart README specifies a realm, type it here. Otherwise, press enter to take the default `ApplicationRealm`.
+ If the quickstart README specifies a realm, type it here. Otherwise, press enter to use the default `ApplicationRealm`.
5. When prompted, enter the the Username and Passord. If the quickstart README specifies a Username nad Password, enter them here. Otherwise, use the default Username `quickstartUser` and Password `quickstartPassword`.
Username : quickstartUser
View
6 bean-validation/README.md
@@ -24,10 +24,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -69,7 +69,7 @@ You can also check the server console output to verify that the Arquillian tests
-Run the Quickstart in JBoss Developer Studio or Eclipse
+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.html/#useeclipse)
View
4 bmt/README.md
@@ -31,10 +31,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
6 cdi-injection/README.md
@@ -5,7 +5,7 @@ Author: Jason Porter
What is it?
-----------
-This example demonstrates the use of *CDI 1.0 Injection and Qualifiers* in *JBoss AS 7* or *JBoss Enterprise Application Platform 6* with JSF as the front-end client.
+This example demonstrates the use of *CDI 1.0 Injection and Qualifiers* in *JBoss Enterprise Application Platform 6* or *JBoss AS 7* with JSF as the front-end client.
System requirements
@@ -21,10 +21,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
10 cmt/README.md
@@ -20,7 +20,7 @@ With CMT, the EJB container sets the boundaries of a transaction. This differs f
### What makes this an example of container managed transactions?
-Take a look at <code>org.jboss.as.quickstarts.cmt.ejb.CustomerManagerEJBImpl</code>. You can see that this stateless session bean has been marked up with an @javax.ejb.TransactionAttribute annotation.
+Take a look at <code>org.jboss.as.quickstarts.cmt.ejb.CustomerManagerEJBImpl</code>. You can see that this stateless session bean has been marked up with the @javax.ejb.TransactionAttribute annotation.
The available options for this annotation are as follows:
@@ -32,7 +32,7 @@ The available options for this annotation are as follows:
* Never - If the client has a transaction running and does not suspend it but calls a method annotated with Never then an EJB exception will be raised.
-JBoss Enterprise Application Platform 6 and JBoss AS 7 ship with an H2 datasource by default. This example shows how to transactionally insert key value pairs into the H2 database and demonstrates the requirements on the developer with respect to the JPA Entity Manager.
+JBoss Enterprise Application Platform 6 and JBoss AS 7 ship with H2, an in-memory database written in Java. This example shows how to transactionally insert key value pairs into the H2 database and demonstrates the requirements on the developer with respect to the JPA Entity Manager.
System requirements
@@ -49,10 +49,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Full Profile
+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 directory.
+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:
For Linux: JBOSS_HOME/bin/standalone.sh -c standalone-full.xml
@@ -91,7 +91,7 @@ The application will be running at the following URL: <http://localhost:8080/jb
You will be presented with a simple form for adding customers to a database.
-After a user is successfully added to the database, a message is produced container the details of the user. An example MDB will dequeue this message and print the contents as such:
+After a user is successfully added to the database, a message is produced containing the details of the user. An example MDB will dequeue this message and print the following contents:
Received Message: Created customer named: Tom with ID: 1
View
8 ejb-in-ear/README.md
@@ -40,10 +40,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -62,7 +62,7 @@ _NOTE: The following build command assumes you have configured your Maven user s
2. Open a command line and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
- mvn clean package jboss-as:deploy
+ mvn clean package jboss-as:deploy
4. This will deploy `target/jboss-as-ejb-in-ear.ear` to the running instance of the server.
@@ -72,7 +72,7 @@ _NOTE: The following build command assumes you have configured your Maven user s
2. Open a command line and navigate to the root directory of this quickstart.
3. Type this command to undeploy the archive:
- mvn jboss-as:undeploy
+ mvn jboss-as:undeploy
Access the application
View
8 ejb-in-war/README.md
@@ -11,8 +11,8 @@ The example follows the common "Hello World" pattern. These are the steps that o
1. A JSF page asks the user for their name.
2. On clicking submit, the name is sent to a managed bean namde `Greeter`.
-3. On setting the name, the `Greeter` invokes the `GreeterEJB`, which was injected to the managed bean. Notice the field annotated with @EJB.
-4. The response from invoking the `GreeterEJB` is stored in a field (message) of the managed bean.
+3. On setting the name, the `Greeter` invokes the `GreeterEJB`, which was injected into the managed bean. Notice the field annotated with `@EJB`.
+4. The response from invoking the `GreeterEJB` is stored in a field `message` of the managed bean.
5. The managed bean is annotated as `@SessionScoped`, so the same managed bean instance is used for the entire session. This ensures that the message is available when the page reloads and is displayed to the user.
System requirements
@@ -29,10 +29,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
6 ejb-remote/README.md
@@ -11,7 +11,7 @@ There are two components to this example:
1. A server side component:
- The server component is comprised of a stateful and a stateless EJB. It provides both an EJB JAR that is deployed to the server and a JAR file containing the remote business interfaces required by the remote client application.
+ The server component is comprised of a stateful EJB and a stateless EJB. It provides both an EJB JAR that is deployed to the server and a JAR file containing the remote business interfaces required by the remote client application.
2. A remote client application that accesses the server component.
The remote client application depends on the remote business interfaces from the server component. This application looks up the stateless and stateful beans via JNDI and invokes a number of methods on them.
@@ -33,10 +33,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
18 ejb-security/README.md
@@ -6,15 +6,15 @@ Author: Sherif F. Makary
What is it?
-----------
-This example demonstrates the use of JEE declarative security to control access to EJB 3 and Security in *JBoss Enterprise Application Platform 6* or *JBoss AS 7*.
+This example demonstrates the use of Java EE declarative security to control access to EJB3 and Security in *JBoss Enterprise Application Platform 6* or *JBoss AS 7*.
-The following are the steps required to implement EJB security:
+This quickstart takes the following steps to implement EJB security:
-1. Use the security domain `other` that is defined in the application server default `standalone.xml` configuration file.
-2. Add the user `quickstartUser` with password `quickstartPassword`, belonging to the role `guest` and realm `ApplicationRealm`. The procedure for adding a user is described below.
-3. A security domain reference for the `other` security domain is added to `WEB-INF/jboss-web.xml`.
-4. A security constraint is added to `WEB-INF/web.xml` .
-5. Security annotations are added to the EJB declaration.
+1. Define a security domain in the `standalone.xml` configuration file.
+2. Add an application user with access rights to the application.
+3. Add a security domain reference to `WEB-INF/jboss-web.xml`.
+4. Add a security constraint to the `WEB-INF/web.xml` .
+5. Add a security annotation to the EJB declaration.
When you review the code, note the allowed user role `guest` in the annotation -`@RolesAllowed`- is the same as the user role defined in step 2 above.
@@ -38,10 +38,10 @@ 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.html/#addapplicationuser)
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
4 forge-from-scratch/README.md
@@ -61,10 +61,10 @@ After this command completes, look in your QUICKSTART_HOME/forge-from-scratch/ f
For a full description of what was generated by running this script and details on the structure of the application, visit the [Forge UI Scaffolding Guide](https://docs.jboss.org/author/display/FORGE/UI+Scaffolding)
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
4 greeter/README.md
@@ -22,10 +22,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
6 h2-console/README.md
@@ -24,12 +24,6 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Additional requirements
------------------------
-
-You will need the H2 Console to run test this quickstart. You can download it from <http://www.h2database.com/html/download.html>. We recommend using the platform independent zip.
-
-
Prerequisites
-----------
View
4 helloworld-errai/README.md
@@ -26,10 +26,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
4 helloworld-gwt/README.md
@@ -24,10 +24,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
4 helloworld-jms/README.md
@@ -33,10 +33,10 @@ Add an Application User
This quickstart uses secured management interfaces and requires that you create an application user to access the running application. Instructions to set up the quickstart application user can be found here: [Add an Application User](../README.html/#addapplicationuser)
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Full Profile
+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 directory.
+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:
For Linux: JBOSS_HOME/bin/standalone.sh -c standalone-full.xml
View
4 helloworld-jsf/README.md
@@ -24,10 +24,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
4 helloworld-mdb/README.md
@@ -24,10 +24,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Full Profile
+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 directory.
+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:
For Linux: JBOSS_HOME/bin/standalone.sh -c standalone-full.xml
View
4 helloworld-osgi/README.md
@@ -22,10 +22,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
10 helloworld-rs/README.md
@@ -22,17 +22,17 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
For Windows: JBOSS_HOME\bin\standalone.bat
-Build and Deploy the Quickstart - Locally
+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.html/#buildanddeploy) for complete instructions and additional options._
@@ -44,7 +44,7 @@ _NOTE: The following build command assumes you have configured your Maven user s
2. Open a command line and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
- mvn clean package jboss-as:deploy
+ mvn clean package jboss-as:deploy
4. This will deploy `target/jboss-as-helloworld-rs.war` to the running instance of the server.
@@ -54,7 +54,7 @@ _NOTE: The following build command assumes you have configured your Maven user s
2. Open a command line and navigate to the root directory of this quickstart.
3. Type this command to undeploy the archive:
- mvn jboss-as:undeploy
+ mvn jboss-as:undeploy
Access the application
View
4 helloworld-singleton/README.md
@@ -22,10 +22,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
6 helloworld/README.md
@@ -7,6 +7,8 @@ What is it?
This example demonstrates the use of *CDI 1.0* and *Servlet 3* in *JBoss Enterprise Application Platform 6* or *JBoss AS 7*.
+There is a tutorial for this quickstart in the [Getting Started Developing Applications Guide](https://docs.jboss.org/author/display/AS71/Getting+Started+Developing+Applications+Guide "Getting Started Developing Applications Guide").
+
System requirements
-------------------
@@ -21,10 +23,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
4 hibernate3/README.md
@@ -30,10 +30,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
8 hibernate4/README.md
@@ -29,7 +29,7 @@ If you have not yet done so, you must [Configure Maven](../README.html/#mavencon
Add the Correct Dependencies
---------------------------
-JBoss Enterprise Application Platform 6 and JBoss AS 7 both provide Hibernate 3, Hibernate 4 (as ORM), and JPA support.
+JBoss Enterprise Application Platform 6 and JBoss AS 7 both provide Hibernate 3, Hibernate 4, and JPA support.
If you use Hibernate 4 packaged within JBoss Enterprise Application Platform 6 or JBoss AS 7, you will need to first import the JPA API.
@@ -51,15 +51,13 @@ For example:
</exclusions>
</dependency>
-You may refer "Adding a new external dependency" located at <http://community.jboss.org/wiki/HackingOnAS7> for further help on adding dependencies.
-
Please note that if you are working with Hibernate 3, the process is different. You will need to bundle the jars since JBoss Enterprise Application Platform 6 and JBoss AS 7 do not ship with Hibernate 3. Refer to the `hibernate3` quickstart for details on how to bundle the JARs.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
2  jts/README.md
@@ -62,7 +62,7 @@ The application servers should both be configured as follows:
3. Make a copy of the this JBoss directory structure to use for the second server.
-Start the JBoss Enterprise Application Platform 6 or JBoss Application Server 7 Servers
+Start the JBoss Enterprise Application Platform 6 or JBoss AS 7 Servers
-------------------------
If you are using Linux:
View
4 kitchensink-ear/README.md
@@ -23,10 +23,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
6 kitchensink-jsp/README.md
@@ -9,7 +9,7 @@ This quickstart is a deployable Maven 3 project to help you get your foot in the
This project is setup to allow you to create a compliant Java EE 6 application using *JSP 2.0* *EL 2.0* *JSTL 1.2* *CDI 1.0*, *EJB 3.1*, *JPA 2.0* and Bean Validation 1.0.
-This project rebuilds the presentation tier of the `kitchensink` quickstart using JSP and JSTL instead of JSF features. It reuses all other components from the Member Registration template. It also reuses the persistence unit and some sample persistence and transaction code to help you with database access in enterprise Java.
+This project recreates the presentation tier of the `kitchensink` quickstart using JSP and JSTL instead of JSF features. It reuses all other components from the Member Registration template. It also reuses the persistence unit and some sample persistence and transaction code to help you with database access in enterprise Java.
System requirements
-------------------
@@ -25,10 +25,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
6 kitchensink/README.md
@@ -10,6 +10,8 @@ This is your project! It is a sample, deployable Maven 3 project to help you get
This project is setup to allow you to create a compliant Java EE 6 application using JSF 2.0, CDI 1.0, EJB 3.1, JPA 2.0 and Bean Validation 1.0. It includes a persistence unit and some sample persistence and transaction code to introduce you to database access in enterprise Java.
+There is a tutorial for this quickstart in the [Getting Started Developing Applications Guide](https://docs.jboss.org/author/display/AS71/Getting+Started+Developing+Applications+Guide "Getting Started Developing Applications Guide").
+
System requirements
-------------------
@@ -24,10 +26,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
4 log4j/README.md
@@ -27,10 +27,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
6 mail/README.md
@@ -9,7 +9,7 @@ This example demonstrates sending email with the use of *CDI 1.0* and *JSF 2.0*
The example uses the default Mail provider that comes out of the box with *JBoss Enterprise Application Platform 6* and *JBoss AS 7*. It uses your local mail relay and the default SMTP port of 25.
-The configuration of the mail provider is found in either *JBOSS_HOME/standalone/configuration.xml* or *JBOSS_HOME/domain/configuration.xml*. An example is provided below:
+The configuration of the mail provider is found in either `JBOSS_HOME/standalone/configuration.xml` or `JBOSS_HOME/domain/configuration.xml`. An example is provided below:
<subsystem xmlns="urn:jboss:domain:mail:1.0">
<mail-session jndi-name="java:jboss/mail/Default" >
@@ -42,10 +42,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
6 numberguess/README.md
@@ -7,6 +7,8 @@ What is it?
This example demonstrates the use of *CDI 1.0* and *JSF 2.0* in *JBoss AS 7* *JBoss Enterprise Application Platform 6*.
+There is a tutorial for this quickstart in the [Getting Started Developing Applications Guide](https://docs.jboss.org/author/display/AS71/Getting+Started+Developing+Applications+Guide "Getting Started Developing Applications Guide").
+
System requirements
-------------------
@@ -21,10 +23,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
4 payment-cdi-event/README.md
@@ -47,10 +47,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
4 richfaces-validation/README.md
@@ -43,10 +43,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
4 servlet-async/README.md
@@ -23,10 +23,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
4 servlet-filterlistener/README.md
@@ -20,10 +20,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
17 servlet-security/README.md
@@ -8,13 +8,14 @@ What is it?
This example demonstrates the use of JEE declarative security to control access to Servlets and Security in JBoss Enterprise Application Platform 6 and JBoss AS7.
-The following are the steps required to implement Servlet security:
+This quickstart takes the following steps to implement Servlet security:
+
+1. Define a security domain in the `standalone.xml` configuration file.
+2. Add an application user with access rights to the application.
+3. Add a security domain reference to `WEB-INF/jboss-web.xml`.
+4. Add a security constraint to the `WEB-INF/web.xml` .
+5. Add a security annotation to the EJB declaration.
-1. Use the security domain `other` that is defined in the application server's default `standalone.xml`
-2. Add the user `quickstartUser` with password `quickstartPassword` belonging to the role `guest` and realm `ApplicationRealm`. The procedure for adding a user is described below.
-3. A security domain reference for the `other` security domain is added to `WEB-INF/jboss-web.xml`
-4. A security constraint is added to `WEB-INF/web.xml`
-5. Security annotations are added to the EJB declaration
Please note the allowed user role `guest` in the annotation -`@RolesAllowed`- is the same as the user role defined in step 2
@@ -39,10 +40,10 @@ 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.html/#addapplicationuser)
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
4 shopping-cart/README.md
@@ -32,10 +32,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
4 tasks-jsf/README.md
@@ -33,10 +33,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
9 template/README.md
@@ -55,16 +55,16 @@ Here are some examples:
If your quickstart requires any other components, you must describe how to configure them here.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7
+Start JBoss Enterprise Application Platform 6 or JBoss AS 7
-------------------------
Does this quickstart require a running server? If so, you must show how to start the server. If you start the server in one of the following 3 ways, you can simply copy the instructions in the README file located in the root folder of the quickstart directory:
- * Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+ * Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile
- * Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Full Profile
+ * Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Full Profile
- * Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with Custom Options. You will need to provide the argument string to pass on the command line, for example:
+ * Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with Custom Options. You will need to provide the argument string to pass on the command line, for example:
`--server-config=../../docs/examples/configs/standalone-xts.xml`
@@ -146,7 +146,6 @@ 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.html/#useeclipse)
-
Debug the Application
------------------------------------
View
4 wicket-ear/README.md
@@ -37,10 +37,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
View
6 wsat-simple/README.md
@@ -21,7 +21,7 @@ It is also assumed that you have an understanding of WS-AtomicTransaction. For m
The application consists of a single JAX-WS web service that is deployed within a WAR archive. It is tested with a JBoss Arquillian enabled JUnit test.
-When running the org.jboss.as.quickstarts.wsat.simple.ClientTest#testCommit() method, the following steps occur:
+When running the `org.jboss.as.quickstarts.wsat.simple.ClientTest#testCommit()` method, the following steps occur:
1. A new Atomic Transaction (AT) is created by the client.
2. An operation on a WS-AT enabled Web service is invoked by the client.
@@ -50,7 +50,7 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Custom Options
+Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Custom Options
----------------------
First, edit the log level to reduce the amount of log output. This should make it easier to read the logs produced by this example. To do this add the
@@ -78,7 +78,7 @@ _NOTE: The following commands assume you have configured your Maven user setting
2. Open a command line and navigate to the root directory of this quickstart.
3. Type the following command to run the test goal with the following profile activated:
- mvn clean test -Parq-jbossas-remote
+ mvn clean test -Parq-jbossas-remote
Investigate the Console Output
View
10 wsba-coordinator-completion-simple/README.md
@@ -17,7 +17,7 @@ This example demonstrates the basics of implementing a WS-BA enabled Web service
For a more complete example, please see the XTS demonstrator application that ships with the JBossTS project: http://www.jboss.org/jbosstm.
-It is also assumed that you have an understanding of WS-BusinessActivity. For more details, read the XTS documentation that ships with the JBossTS project, which can be downloaded here: http://www.jboss.org/jbosstm/downloads/JBOSSTS_4_16_0_Final
+It is also assumed that you have an understanding of WS-BusinessActivity. For more details, read the XTS documentation that ships with the JBossTS project, which can be downloaded here: <http://www.jboss.org/jbosstm/downloads/JBOSSTS_4_16_0_Final>
The application consists of a single JAX-WS web service that is deployed within a WAR archive. It is tested with a JBoss Arquillian enabled JUnit test.
@@ -25,12 +25,12 @@ When running the org.jboss.as.quickstarts.wsba.coordinatorcompletion.simple.Clie
1. A new Business Activity is created by the client.
2. Multiple operations on a WS-BA enabled Web service is invoked by the client.
-3. The JaxWSHeaderContextProcessor in the WS Client handler chain inserts the BA context into the outgoing SOAP messages.
-4. When the service receives a SOAP request, the JaxWSHeaderContextProcessor in its handler chain inspects the BA context and associates the request with this BA.
+3. The `JaxWSHeaderContextProcessor` in the WS Client handler chain inserts the BA context into the outgoing SOAP messages.
+4. When the service receives a SOAP request, the `JaxWSHeaderContextProcessor` in its handler chain inspects the BA context and associates the request with this BA.
5. The Web service operation is invoked.
6. For the first request, in this BA, A participant is enlisted in this BA. This allows the Web Service logic to respond to protocol events, such as compensate and close.
7. The service invokes the business logic. In this case, a String value is added to the set.
-9. The client can then make additional calls to the SetService. As the SetService participates as a CoordinatorCompletion protocol, it will continue to accept calls to `addValueToSet` until it is told to complete by the coordinator.
+9. The client can then make additional calls to the `SetService`. As the `SetService` participates as a `CoordinatorCompletion` protocol, it will continue to accept calls to `addValueToSet` until it is told to complete by the coordinator.
10. The client can then decide to complete or cancel the BA.
* If the client decides to complete, all participants will be told to complete. Providing all participants successfully complete, the coordinator will then tell all participants to close, otherwise the completed participants will be told to compensate.
* If the participant decides to cancel, all participants will be told to compensate.
@@ -52,7 +52,7 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Custom Options
+Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Custom Options
----------------------
Next you need to start JBoss Enterprise Application Platform 6 or JBoss AS 7 (7.1.0.CR1 or above), with the XTS sub system enabled. This is enabled through the optional server configuration *standalone-xts.xml*. To do this, run the following commands from the top-level directory of JBossAS:
View
8 wsba-participant-completion-simple/README.md
@@ -28,13 +28,13 @@ following steps occur:
1. A new Business Activity is created by the client.
2. An operation on a WS-BA enabled Web service is invoked by the client.
-3. The JaxWSHeaderContextProcessor in the WS Client handler chain inserts the BA context into the outgoing SOAP message.
-4. When the service receives the SOAP request, the JaxWSHeaderContextProcessor in its handler chain inspects the BA context and associates the request with this BA.
+3. The `JaxWSHeaderContextProcessor` in the WS Client handler chain inserts the BA context into the outgoing SOAP message.
+4. When the service receives the SOAP request, the `JaxWSHeaderContextProcessor` in its handler chain inspects the BA context and associates the request with this BA.
5. The Web service operation is invoked.
6. A participant is enlisted in this BA. This allows the Web Service logic to respond to protocol events, such as compensate and close.
7. The service invokes the business logic. In this case, a String value is added to the set.
8. The backend resource is prepared. This ensures that the Backend resource can undo or make permanent the change when told to do so by the coordinator.
-9. Providing the above steps where successful, the service notifies the coordinator that it has completed. The service has now made its changes visible and is not holding any locks. Allowing the service to notify completion is an optimisation that prevents the holding of locks, whilst waiting for other participants to complete. This notification is required as the Service participates in the ParticipantCompletion protocol.
+9. Providing the above steps where successful, the service notifies the coordinator that it has completed. The service has now made its changes visible and is not holding any locks. Allowing the service to notify completion is an optimisation that prevents the holding of locks, whilst waiting for other participants to complete. This notification is required as the Service participates in the `ParticipantCompletion` protocol.
10. The client can then decide to complete or cancel the BA. If the client decides to complete, all participants will be told to close. If the participant decides to cancel, all participants will be told to compensate.
There are other tests that show:
@@ -57,7 +57,7 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Custom Options
+Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Custom Options
----------------------
Next you need to start JBoss Enterprise Application Platform 6 or JBoss AS 7 (7.1.0.CR1 or above), with the XTS sub system enabled. This is enabled through the optional server configuration *standalone-xts.xml*. To do this, run the following commands from the top-level directory of JBossAS:
View
4 xml-jaxp/README.md
@@ -22,10 +22,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](../README.html/#mavenconfiguration) before testing the quickstarts.
-Start JBoss Enterprise Application Platform 6 or JBoss Application Server 7 with the Web Profile
+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 directory.
+1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh
Please sign in to comment.
Something went wrong with that request. Please try again.