[richfaces-svn-commits] JBoss Rich Faces SVN: r9866 - in trunk/samples/richfaces-demo/src/main/webapp/richfaces: beanValidator and 1 other directories.

Author: smukhina Date: 2008-08-01 11:24:19 -0400 (Fri, 01 Aug 2008) New Revision: 9866 Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/ajaxValidator/usage.xhtml trunk/samples/richfaces-demo/src/main/webapp/richfaces/beanValidator/usage.xhtml trunk/samples/richfaces-demo/src/main/webapp/richfaces/graphValidator/usage.xhtml Log: https://jira.jboss.org/jira/browse/RF-398- language is corrected for new livedemo components Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/ajaxValidator/usage.xhtml =================================================================== --- trunk/samples/richfaces-demo/src/main/webapp/richfaces/ajaxValidator/usage.xhtml 2008-08-01 15:15:35 UTC (rev 9865) +++ trunk/samples/richfaces-demo/src/main/webapp/richfaces/ajaxValidator/usage.xhtml 2008-08-01 15:24:19 UTC (rev 9866) @@ -10,13 +10,13 @@ <p> rich:ajaxValidator is a component designed in order to provide ajax validation - inside the inputs. It designed like a4j:support component but skips all JSF processing + inside the inputs. It is designed like an a4j:support component but skips all JSF processing except validation. </p> <p> - Look to the first simple example. This component should be added as child component - to input which should be validated and specify validation event. The component - is ajaxSingle by default so only current field will be validated. + Look to the first simple example. This component should be added as a child component + to input that should be validated and specify validation event. The component + is ajaxSingle by default so only the current field will be validated. </p> <fieldset class="demo_fieldset"> <legend class="demo_legend">Title</legend> @@ -28,10 +28,10 @@ </div> </fieldset> <p> - The component also provide possibility to use Hibernate Validation for the target fileds. + The component also provides a possibility to use Hibernate Validation for the target fields. </p> <p> - Look to the next examlpe which is modified in order to use Hibernate Validators: + Look to the next example which is modified in order to use Hibernate Validators: </p> <fieldset class="demo_fieldset"> <legend class="demo_legend">Title</legend> Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/beanValidator/usage.xhtml =================================================================== --- trunk/samples/richfaces-demo/src/main/webapp/richfaces/beanValidator/usage.xhtml 2008-08-01 15:15:35 UTC (rev 9865) +++ trunk/samples/richfaces-demo/src/main/webapp/richfaces/beanValidator/usage.xhtml 2008-08-01 15:24:19 UTC (rev 9866) @@ -10,13 +10,13 @@ <p> Starting from 3.2.2 GA version Rich Faces provides support for model-based - constraints defined using Hibernate Validator. So it's possible to use Hibernate + constraints defined using Hibernate Validator. Thus it's possible to use Hibernate Validators the same as for Seam based applications. </p> <p> rich:beanValidator component should be defined in the same way as any JSF validators. - Lock through the example below. + Look through the example below. </p> <fieldset class="demo_fieldset"> <legend class="demo_legend">Title</legend> Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/graphValidator/usage.xhtml =================================================================== --- trunk/samples/richfaces-demo/src/main/webapp/richfaces/graphValidator/usage.xhtml 2008-08-01 15:15:35 UTC (rev 9865) +++ trunk/samples/richfaces-demo/src/main/webapp/richfaces/graphValidator/usage.xhtml 2008-08-01 15:24:19 UTC (rev 9866) @@ -9,11 +9,11 @@ <ui:define name="sample"> <p> - Graph validator component also allow to register Hibernate Validators for the - input components. As opposite to beanValidator which should be - child component for the input to be validated this component should wrap - some subtree with inputs. As result validator for every input in this - subtree will be added to component. + Graph validator component also allows to register Hibernate Validators for the + input components. As opposite to beanValidator that should be + a child component for the input to be validated this component should wrap + some subtree with inputs. As a result validator for every input in this + subtree will be added to the component. </p> <p> Look through the next simple example: @@ -33,13 +33,13 @@ </div> </fieldset> <p> - There is one additional usefull feature in Graph Validator component. + There is one additional useful feature in Graph Validator component. Value attribute could be defined with some value binding to bean. And the bean properties will be validated again <b>after</b> model update. </p> <p> - Simple example of such usage below. Just write some activities of the day - and the time you spend to each one in a day. + Simple example of such kind of usage is shown below. Just write some activities of the day + and the time you spend on each one in a day. </p> <fieldset class="demo_fieldset"> <legend class="demo_legend">Title</legend> @@ -51,11 +51,11 @@ </div> </fieldset> <p> - In this case only properties of each passTime(values of the inputs) validated + In this case only properties of each passTime(values of the inputs) is validated at validation phase. - But after the model updated (Each explicit passtime was validated ok) all the - properties including "TotalTime" validated again. And total validation could - fails if the sum of the hours in a day more than 24. + But after the model is updated (Each explicit passtime was validated ok) all the + properties including "TotalTime" are validated again. And total validation could + fail if the sum of the hours in a day more than 24. </p> </ui:define>