WFK2-784: Update versions of JSF and RichFaces, plus remove redundant…

… line from kitchensink-rf

helloworld-rf/README.md

@@ -3,15 +3,15 @@ helloworld-rf: Helloworld with a JSF Richfaces Front End
 Author: Brian Leathem  
 Level: Beginner  
 Technologies: CDI, JSF, RichFaces  
-Summary: The `helloworld-rf` quickstart demonstrates how to create a Java EE 6 compliant application using JSF 2.0, CDI 1.0, and AJAX-enabled RichFaces 4.1.  
+Summary: The `helloworld-rf` quickstart demonstrates how to create a Java EE 6 compliant application using JSF 2.1, CDI 1.0, and AJAX-enabled RichFaces 4.5.  
 Target Product: WFK  
 Product Versions: EAP 6.1, EAP 6.2, EAP 6.3, WFK 2.7  
 Source: <https://github.com/richfaces/jdf-quickstarts>  
 
 What is it?
 -----------
 
-The `helloworld-rf` quickstart is based on the `helloworld` quickstart, but demonstrates how to create a Java EE 6 compliant application using JSF 2.0, CDI 1.0, and RichFaces 4.1.
+The `helloworld-rf` quickstart is based on the `helloworld` quickstart, but demonstrates how to create a Java EE 6 compliant application using JSF 2.1, CDI 1.0, and RichFaces 4.5.
 
 In this example, a standard JSF `h:inputText` component is AJAX enabled using the RichFaces `a4j:ajax tag`. This triggers the application server to re-render only a subsection of the page on a browser event.
 

kitchensink-deltaspike/README.md

@@ -11,7 +11,7 @@ Source: <https://github.com/jboss-developer/jboss-wfk-quickstarts/>
 What is it?
 -----------
 
-The `kitchensink-deltaspike` quickstart is a deployable Maven 3 project that demonstrates how to create a compliant Java EE 6 application using JSF 2.0, CDI 1.0, JPA 2.0 and Bean Validation 1.0. It uses the `kitchensink` quickstart as its starting point, however, rather than using a Stateless EJB, it leverages the DeltaSpike @Transactional annotation to give transactional behavior to a CDI bean. The entity manager is managed by the application rather than the container. 
+The `kitchensink-deltaspike` quickstart is a deployable Maven 3 project that demonstrates how to create a compliant Java EE 6 application using JSF 2.1, CDI 1.0, JPA 2.0 and Bean Validation 1.0. It uses the `kitchensink` quickstart as its starting point, however, rather than using a Stateless EJB, it leverages the DeltaSpike @Transactional annotation to give transactional behavior to a CDI bean. The entity manager is managed by the application rather than the container. 
 
 The DeltaSpike project (http://incubator.apache.org/deltaspike) consists of a number of portable CDI extensions that provide useful features for Java application developers.
 

kitchensink-rf/README.md

@@ -3,17 +3,15 @@ kitchensink-rf: Kitchensink With a JSF Richfaces Front End
 Author: Pete Muir, Brian Leathem  
 Level: Intermediate  
 Technologies: CDI, JSF, JPA, EJB, JPA, JAX-RS, BV, RichFaces  
-Summary: The `kitchensink-rf` quickstart demonstrates a Java EE 6 application using JSF 2.0 with Richfaces 4, CDI 1.0, EJB 3.1, JPA 2.0 and Bean Validation 1.0.  
+Summary: The `kitchensink-rf` quickstart demonstrates a Java EE 6 application using JSF 2.1 with Richfaces 4.5, CDI 1.0, EJB 3.1, JPA 2.0 and Bean Validation 1.0.  
 Target Product: WFK  
 Product Versions: EAP 6.1, EAP 6.2, EAP 6.3, WFK 2.7  
 Source: <https://github.com/richfaces/jdf-quickstarts>  
 
 What is it?
 -----------
 
-The `kitchensink-rf` quickstart is based on the `kitchensink` quickstart, but demonstrates how to create a Java EE 6 compliant application using JSF 2.0, CDI 1.0, and RichFaces 4.1.
-
-This project is setup to allow you to create a compliant Java EE 6 application using JSF 2.0 with RichFaces 4, 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.
+The `kitchensink-rf` quickstart is based on the `kitchensink` quickstart, but demonstrates how to create a Java EE 6 compliant application using JSF 2.1, CDI 1.0, RichFaces 4.5. It includes a persistence unit and some sample persistence and transaction code to introduce you to database access in enterprise Java.
 
 This application builds on top of the standard JSF approach, by incorporating the RichFaces project to provide a set of components, allowing for a rich user experience.  RichFaces builds on top of the JSF standard, and is a fully portable solution compatible with all JSF implementations.
 

richfaces-validation/README.md

@@ -3,22 +3,22 @@ richfaces-validation: RichFaces and Bean Validation
 Author: Lukas Fryc  
 Level: Beginner  
 Technologies: RichFaces  
-Summary: The `richfaces-validation` quickstart demonstrates how to use JSF 2.0, RichFaces 4.2, CDI 1.0, JPA 2.0 and Bean Validation 1.0.  
+Summary: The `richfaces-validation` quickstart demonstrates how to use JSF 2.1, RichFaces 4.5, CDI 1.0, JPA 2.0 and Bean Validation 1.0.  
 Target Product: WFK  
 Product Versions: EAP 6.1, EAP 6.2, EAP 6.3, WFK 2.7  
 Source: <https://github.com/richfaces/as-quickstarts>  
 
 What is it?
 -----------
 
-The `richfaces-validation` quickstart demonstrates how to use JSF 2.0, RichFaces 4.2, CDI 1.0, JPA 2.0 and Bean Validation 1.0. 
+The `richfaces-validation` quickstart demonstrates how to use JSF 2.1, RichFaces 4.5, CDI 1.0, JPA 2.0 and Bean Validation 1.0. 
 
 It consists of one entity, `Member`, which is annotated with JSR-303 (Bean Validation) constraints. In typical applications, these constraints are checked in several places:
 
 * As database constraints
 * In the persistence layer
 * In the view layer (using JSF / Bean Validation integration)
-* On the client (using RichFaces 4.2 - Client Side Validation)
+* On the client (using RichFaces 4.5 - Client Side Validation)
 
 This ensures the constraints are applied consistently, across all layers, allowing clear and precise error reporting, while not breaking the DRY (Don't Repeat Yourself) principle.