Bz1092026: Update README Target Product metadata value, remove Produc…

…t Versions metadata, and make sure the full product name is near the top of the files.

app-client/README.md

@@ -4,15 +4,14 @@ Author: Wolf-Dieter Fink
 Level: Intermediate  
 Technologies: EJB, EAR, AppClient  
 Summary: The `app-client` quickstart demonstrates how to code and package a client app and use the JBoss EAP client container to start the client Main program.  
-Target Product: EAP  
-Product Versions: EAP 6.1, EAP 6.2, EAP 6.3, EAP 6.4  
+Target Product: JBoss EAP  
 Source: <https://github.com/jboss-developer/jboss-eap-quickstarts/>  
 
 
 What is it?
 -----------
 
-The `app-client` quickstart demonstrates how to use the JBoss EAP client container to start the client 'Main' program and provide Dependency Injections (DI) for client applications. It also shows you how to use Maven to package the application according to the JavaEE specification.
+The `app-client` quickstart demonstrates how to use the JBoss EAP client container to start the client 'Main' program and provide Dependency Injections (DI) for client applications in Red Hat JBoss Enterprise Application Platform. It also shows you how to use Maven to package the application according to the JavaEE specification.
 
 
 This example consists of the following Maven projects, each with a shared parent:

bean-validation-custom-constraint/README.md

@@ -4,14 +4,13 @@ Author: Giriraj Sharma
 Level: Beginner  
 Technologies: CDI, JPA, BV  
 Summary: The `bean-validation-custom-constraint` quickstart demonstrates how to use the Bean Validation API to define custom constraints and validators.  
-Target Product: EAP  
-Product Versions: EAP 6.1, EAP 6.2, EAP 6.3, EAP 6.4  
+Target Product: JBoss EAP  
 Source: <https://github.com/jboss-developer/jboss-eap-quickstarts/>  
 
 What is it?
 -----------
 
-The `bean-validation-custom-constraint` quickstart demonstrates how to use CDI 1.0, JPA 2.0 and Bean Validation 1.0. Bean Validation API allows the developers to define their own constraints by creating a new annotation and writing the validator which is used to validate the value. This quickstart will show you how to create custom constraints and then use it to validate your data. It includes a persistence unit and some sample persistence code to introduce you to database access in enterprise Java. 
+The `bean-validation-custom-constraint` quickstart demonstrates how to use CDI 1.0, JPA 2.0 and Bean Validation 1.0 in Red Hat JBoss Enterprise Application Platform. Bean Validation API allows the developers to define their own constraints by creating a new annotation and writing the validator which is used to validate the value. This quickstart will show you how to create custom constraints and then use it to validate your data. It includes a persistence unit and some sample persistence code to introduce you to database access in enterprise Java. 
 
 This quickstart does not contain a user interface layer. The purpose of this project is to show you how to test bean validation using custom constraints with Arquillian. In this quickstart, the personAddress field of entity Person is validated using a set of custom constraints defined in the class AddressValidator. If you want to see an example of how to test bean validation with a user interface, look at the [kitchensink](../kitchensink/README.md) example.
 

bean-validation/README.md

@@ -4,14 +4,13 @@ Author: Karel Piwko
 Level: Beginner  
 Technologies: CDI, JPA, BV  
 Summary: The `bean-validation` quickstart provides Arquillian tests to demonstrate how to use CDI 1.0, JPA 2.0 and Bean Validation 1.0.  
-Target Product: EAP  
-Product Versions: EAP 6.1, EAP 6.2, EAP 6.3, EAP 6.4  
+Target Product: JBoss EAP  
 Source: <https://github.com/jboss-developer/jboss-eap-quickstarts/>  
 
 What is it?
 -----------
 
-The `bean-validation` quickstart demonstrates how to use CDI 1.0, JPA 2.0 and Bean Validation 1.0. It includes a persistence unit and some sample persistence code to introduce you to database access in enterprise Java. 
+The `bean-validation` quickstart demonstrates how to use CDI 1.0, JPA 2.0 and Bean Validation 1.0 in Red Hat JBoss Enterprise Application Platform. It includes a persistence unit and some sample persistence code to introduce you to database access in enterprise Java. 
 
 This quickstart does not contain a user interface layer. The purpose of this project is to show you how to test bean validation with Arquillian. If you want to see an example of how to test bean validation with a user interface, look at the [kitchensink](../kitchensink/README.md) example.
 

bmt/README.md

@@ -4,17 +4,16 @@ Author: Mike Musgrove
 Level: Intermediate  
 Technologies: EJB, BMT  
 Summary: The `bmt` quickstart demonstrates Bean-Managed Transactions (BMT), showing how to manually manage transaction demarcation while accessing JPA entities.  
-Target Product: EAP  
-Product Versions: EAP 6.1, EAP 6.2, EAP 6.3, EAP 6.4  
+Target Product: JBoss EAP  
 Source: <https://github.com/jboss-developer/jboss-eap-quickstarts/>  
 
 What is it?
 -----------
 
-On occasion, the application developer requires finer grained control over the lifecycle of JTA transactions and JPA Entity Managers than the defaults provided by the Java EE container. This example shows how the developer can override these defaults and take control of aspects of the lifecycle of JPA and transactions.
-
 The `bmt` quickstart demonstrates how to manually manage transaction demarcation while accessing JPA entities in Red Hat JBoss Enterprise Application Platform.
 
+On occasion, the application developer requires finer grained control over the lifecycle of JTA transactions and JPA Entity Managers than the defaults provided by the Java EE container. This example shows how the developer can override these defaults and take control of aspects of the lifecycle of JPA and transactions.
+
 When you run this example, you will be provided with a `Use bean managed Entity Managers` checkbox.
 * If you check the checkbox, it shows the developer responsibilities when injecting an Entity Manager into a managed (stateless) bean.
 * If you uncheck the checkbox, shows the developer responsibilities when using JPA and transactions with an unmanaged component.

cdi-alternative/README.md

@@ -4,14 +4,13 @@ Author: Nevin Zhu
 Level: Intermediate  
 Technologies: CDI, Servlet, JSP  
 Summary: The `cdi-alternative` quickstart demonstrates how to create a bean that can be implemented for different purposes without changing the source code.   
-Target Product: EAP  
-Product Versions: EAP 6.1, EAP 6.2, EAP 6.3, EAP 6.4  
+Target Product: JBoss EAP  
 Source: <https://github.com/jboss-developer/jboss-eap-quickstarts/>  
 
 What is it?
 -----------
 
-The `cdi-alternative` quickstart demonstrates how to create a bean that can be implemented for different purposes without changing the source code. Instead, you choose the bean implementation during development by injecting a qualifier. Then at deployment time, rather than modify the source code, you choose the alternative.
+The `cdi-alternative` quickstart demonstrates how to create a bean that can be implemented for different purposes without changing the source code in Red Hat JBoss Enterprise Application Platform. Instead, you choose the bean implementation during development by injecting a qualifier. Then at deployment time, rather than modify the source code, you choose the alternative.
 
 Alternatives are commonly used for purposes like the following:
 

cdi-decorator/README.md

@@ -4,16 +4,17 @@ Author: Ievgen Shulga
 Level: Intermediate  
 Technologies: CDI, JSF  
 Summary: The `cdi-decorator` quickstart demonstrates the use of a CDI Decorator to intercept bean methods and modify the business logic.  
-Target Product: EAP  
-Product Versions: EAP 6.1, EAP 6.2, EAP 6.3, EAP 6.4  
+Target Product: JBoss EAP  
 Source: <https://github.com/jboss-developer/jboss-eap-quickstarts/>  
 
 What is it?
 -----------
-The `cdi-decorator` quickstart demonstrates the use of CDI Decorator.
+The `cdi-decorator` quickstart demonstrates the use of CDI Decorator in Red Hat JBoss Enterprise Application Platform.
+
 It represents a common decorator design pattern. We take a class and we wrap decorator class around it. 
 When we call the class, we always pass through the surrounding decorator class before we reach the inner class. 
 In this example, the decorator class simply changes the staff bonus from '100' to '200' and the staff position from 'Java Developer' to 'Team Lead'. It then logs a message to the server console.
+
 By default, all decorators are disabled, so application will run without using decorator. We need to enable our decorator in the 'beans.xml' descriptor to make it work.
 
 

cdi-injection/README.md

@@ -4,8 +4,7 @@ Author: Jason Porter
 Level: Beginner  
 Technologies: CDI  
 Summary: The `cdi-injection` quickstart demonstrates the use of *CDI 1.0 Injection and Qualifiers* in JBoss EAP with a JSF front-end client.  
-Target Product: EAP  
-Product Versions: EAP 6.1, EAP 6.2, EAP 6.3, EAP 6.4  
+Target Product: JBoss EAP  
 Source: <https://github.com/jboss-developer/jboss-eap-quickstarts/>  
 
 What is it?

cdi-interceptors/README.md

@@ -4,14 +4,13 @@ Author: Ievgen Shulga
 Level: Intermediate  
 Technologies: JPA, JSF, EJB  
 Summary: The `cdi-interceptors` quickstart demonstrates how to use CDI interceptors for cross-cutting concerns such as logging and simple auditing.  
-Target Product: EAP  
-Product Versions: EAP 6.1, EAP 6.2, EAP 6.3, EAP 6.4  
+Target Product: JBoss EAP  
 Source: <https://github.com/jboss-developer/jboss-eap-quickstarts/>  
 
 What is it?
 -----------
 
-The `cdi-interceptors` quickstart demonstrates using CDI interceptors for cross-cutting concerns such as logging and simple auditing. 
+The `cdi-interceptors` quickstart demonstrates how to use CDI interceptors for cross-cutting concerns such as logging and simple auditing in applications deployed to Red Hat JBoss Enterprise Application Platform. 
 Interceptors can be applied to any business methods or beans, simply by adding appropriate interceptor binding type annotation. The project contains EJB service that can create and retrieve object from database.
 This example demonstrates 2 interceptors: `AuditInterceptor` and `LoggingInterceptor`
 

cdi-portable-extension/README.md

@@ -4,15 +4,15 @@ Author: Jason Porter
 Level: Intermediate  
 Technologies: CDI  
 Summary: The `cdi-portable-extension` quickstart demonstrates a simple CDI Portable Extension that uses SPI classes to inject beans with data from an XML file.  
-Target Product: EAP  
-Product Versions: EAP 6.1, EAP 6.2, EAP 6.3, EAP 6.4  
+Target Product: JBoss EAP  
 Source: <https://github.com/jboss-developer/jboss-eap-quickstarts/>  
 
 What is it?
 -----------
 
 The `cdi-portable-extension` quickstart demonstrates a simple CDI Portable Extension and some of the SPI classes used
-to complete that task. This particular extension explores the ProcessInjectionTarget and 
+to complete that task in an application deployed to Red Hat JBoss Enterprise Application Platform. 
+This particular extension explores the ProcessInjectionTarget and 
 InjectionTarget SPI classes of CDI, to demonstrate a possible way to seed data into beans.
 
 A Portable Extension is essentially an extension to Java EE 6+ which is tailored to a specific

cdi-stereotype/README.md

@@ -4,14 +4,15 @@ Author: Ievgen Shulga
 Level: Intermediate  
 Technologies: JPA, JSF, EJB  
 Summary: The `cdi-stereotype` quickstart demonstrates how to apply CDI stereotypes to beans to encapsulate CDI interceptor bindings and CDI alternatives.  
-Target Product: EAP  
-Product Versions: EAP 6.1, EAP 6.2, EAP 6.3, EAP 6.4  
+Target Product: JBoss EAP  
 Source: <https://github.com/jboss-developer/jboss-eap-quickstarts/>  
 
 What is it?
 -----------
 
-The `cdi-stereotype` quickstart is an extension of the [cdi-interceptors](../cdi_interceptors/README.md) quickstart and demonstrates how to use a CDI stereotype. A stereotype is an annotation, annotated `@Stereotype`, that packages several other annotations. Stereotypes allow a developer to declare common metadata for beans in a central place. 
+The `cdi-stereotype` quickstart is an extension of the [cdi-interceptors](../cdi_interceptors/README.md) quickstart and demonstrates how to use a CDI stereotype in Red Hat JBoss Enterprise Application Platform. 
+
+A stereotype is an annotation, annotated `@Stereotype`, that packages several other annotations. Stereotypes allow a developer to declare common metadata for beans in a central place. 
 
 In this example, the stereotype encapsulates the following :
 

cdi-veto/README.md

@@ -4,15 +4,15 @@ Author: Jason Porter
 Level: Intermediate  
 Technologies: CDI  
 Summary: The `cdi-veto` quickstart is a simple CDI Portable Extension that uses SPI classes to show how to remove beans and inject JPA entities into an application.  
-Target Product: EAP  
-Product Versions: EAP 6.1, EAP 6.2, EAP 6.3, EAP 6.4  
+Target Product: JBoss EAP  
 Source: <https://github.com/jboss-developer/jboss-eap-quickstarts/>  
 
 What is it?
 -----------
 
 The `cdi-veto` quickstart demonstrates a simple CDI Portable Extension and some of the SPI classes used
-to complete that task. This particular extension explores the ProcessInjectionTarget and
+to complete that task in an application deployed to Red Hat JBoss Enterprise Application Platform. 
+This particular extension explores the ProcessInjectionTarget and
 InjectionTarget SPI classes of CDI to demonstrate removing a bean from CDI's knowledge and
 correctly injecting JPA entities in your application.
 

cluster-ha-singleton/README.md

@@ -4,15 +4,14 @@ Author: Wolf-Dieter Fink
 Level: Advanced  
 Technologies: EJB, HASingleton, JNDI  
 Summary: The `cluster-ha-singleton` quickstart deploys a Service, wrapped with the SingletonService decorator, and used as a cluster-wide singleton service.  
-Target Product: EAP  
-Product Versions: EAP 6.1, EAP 6.2, EAP 6.3, EAP 6.4  
+Target Product: JBoss EAP  
 Source: <https://github.com/jboss-developer/jboss-eap-quickstarts/>  
 
 What is it?
 -----------
 
 The `cluster-ha-singleton` quickstart demonstrates the deployment of a Service that is wrapped with the 
-SingletonService decorator and used as a cluster-wide singleton service.
+SingletonService decorator and used as a cluster-wide singleton service in Red Hat JBoss Enterprise Application Platform.
 The service activates a scheduled timer, which is started only once in the cluster.
 
 The example is composed of a Maven subproject and a parent project. The projects are as follows:

cmt/README.md

@@ -4,13 +4,12 @@ Author: Tom Jenkinson
 Level: Intermediate  
 Technologies: EJB, CMT  
 Summary: The `cmt` quickstart demonstrates Container-Managed Transactions (CMT), showing how to use transactions managed by the container.  
-Target Product: EAP  
-Product Versions: EAP 6.1, EAP 6.2, EAP 6.3, EAP 6.4  
+Target Product: JBoss EAP  
 Source: <https://github.com/jboss-developer/jboss-eap-quickstarts/>  
 
 ## What is it?
 
-The `cmt` quickstart demonstrates using transactions managed by the container. It is a fairly typical scenario of updating a database and sending a JMS message in the same transaction. A simple MDB is provided that prints out the message sent but this is not a transactional MDB and is purely provided for debugging purposes.
+The `cmt` quickstart demonstrates using transactions managed by the container in Red Hat JBoss Enterprise Application Platform. It is a fairly typical scenario of updating a database and sending a JMS message in the same transaction. A simple MDB is provided that prints out the message sent but this is not a transactional MDB and is purely provided for debugging purposes.
 
 Aspects touched upon in the code:
 

ejb-asynchronous/README.md

@@ -4,14 +4,13 @@ Author: Wolf-Dieter Fink
 Level: Advanced  
 Technologies: Asynchronous EJB  
 Summary: The `ejb-asynchronous` quickstart demonstrates the behavior of asynchronous EJB invocations by a deployed EJB and a remote client and how to handle errors.  
-Target Product: EAP  
-Product Versions: EAP 6.1, EAP 6.2, EAP 6.3, EAP 6.4  
+Target Product: JBoss EAP  
 Source: <https://github.com/jboss-developer/jboss-eap-quickstarts/>  
 
 What is it?
 -----------
 
-The `ejb-asynchronous` quickstart demonstrates the behavior of asynchronous EJB invocations. The methods are invoked by both an EJB in the deployment and by a remote client. The quickstart also shows error handling if the asynchronous method invocation fails.
+The `ejb-asynchronous` quickstart demonstrates the behavior of asynchronous EJB invocations in Red Hat JBoss Enterprise Application Platform. The methods are invoked by both an EJB in the deployment and by a remote client. The quickstart also shows error handling if the asynchronous method invocation fails.
 
 The example is composed of 2 Maven modules, each with a shared parent. The modules are as follows:
 

ejb-in-ear/README.md

@@ -4,8 +4,7 @@ Author: Paul Robinson
 Level: Intermediate  
 Technologies: EJB, EAR  
 Summary: The `ejb-in-ear` quickstart demonstrates how to deploy an EAR archive that contains a *JSF 2.1* WAR and an *EJB 3.1* JAR.  
-Target Product: EAP  
-Product Versions: EAP 6.1, EAP 6.2, EAP 6.3, EAP 6.4  
+Target Product: JBoss EAP  
 Source: <https://github.com/jboss-developer/jboss-eap-quickstarts/>  
 
 What is it?

ejb-in-war/README.md

@@ -4,8 +4,7 @@ Author: Paul Robinson
 Level: Intermediate  
 Technologies: EJB, JSF, WAR  
 Summary: The `ejb-in-war` quickstart demonstrates how to package an *EJB 3.1* bean in a WAR archive and deploy it to JBoss EAP. Arquillian tests are also provided.  
-Target Product: EAP  
-Product Versions: EAP 6.1, EAP 6.2, EAP 6.3, EAP 6.4  
+Target Product: JBoss EAP  
 Source: <https://github.com/jboss-developer/jboss-eap-quickstarts/>  
 
 What is it?

ejb-multi-server/README.md

@@ -4,15 +4,14 @@ Author: Wolf-Dieter Fink
 Level: Advanced  
 Technologies: EJB, EAR  
 Summary: The `ejb-multi-server` quickstart shows how to communicate between multiple applications deployed to different servers using an EJB to log the invocation.  
-Target Product: EAP  
-Product Versions: EAP 6.1, EAP 6.2, EAP 6.3, EAP 6.4  
+Target Product: JBoss EAP  
 Source: <https://github.com/jboss-developer/jboss-eap-quickstarts/>  
 
 
 What is it?
 -----------
 
-The `ejb-multi-server` quickstart demonstrates communication between applications deployed to different servers. Each application is deployed as an EAR and contains a simple EJB3.1 bean. The only function of each bean is to log the invocation.
+The `ejb-multi-server` quickstart demonstrates communication between applications deployed to different Red Hat JBoss Enterprise Application Platform servers. Each application is deployed as an EAR and contains a simple EJB3.1 bean. The only function of each bean is to log the invocation.
 
 This example consists of the following Maven projects, each with a shared parent:
 

ejb-remote/README.md

@@ -4,8 +4,7 @@ Author: Jaikiran Pai, Mike Musgrove
 Level: Intermediate  
 Technologies: EJB, JNDI  
 Summary: The `ejb-remote` quickstart uses *EJB 3.1* and *JNDI* to demonstrate how to access an EJB, deployed to JBoss EAP, from a remote Java client application.  
-Target Product: EAP  
-Product Versions: EAP 6.1, EAP 6.2, EAP 6.3, EAP 6.4  
+Target Product: JBoss EAP  
 Source: <https://github.com/jboss-developer/jboss-eap-quickstarts/>  
 
 What is it?

ejb-security-interceptors/README.md

@@ -4,14 +4,13 @@ Author: Darran Lofthouse
 Level: Advanced  
 Technologies: EJB, Security  
 Summary: The `ejb-security-interceptors` quickstart demonstrates how to use client and server side interceptors to switch the identity for an EJB call.  
-Target Product: EAP  
-Product Versions: EAP 6.3, EAP 6.4  
+Target Product: JBoss EAP  
 Source: <https://github.com/jboss-developer/jboss-eap-quickstarts/>  
 
 What is it?
 -----------
 
-The `ejb-security-interceptors` quickstart demonstrates how to use client and server side interceptors to switch the identity for an EJB call.
+The `ejb-security-interceptors` quickstart demonstrates how to use client and server side interceptors to switch the identity for an EJB call in Red Hat JBoss Enterprise Application Platform.
 
 By default, when you make a remote call to an EJB deployed to the application server, the connection to the server is authenticated and any request received over this connection is executed as the identity that authenticated the connection. This is true for both client-to-server and server-to-server calls. If you need to use different identities from the same client, you normally need to open multiple connections to the server so that each one is authenticated as a different identity.