You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by hu...@apache.org on 2003/12/11 21:37:47 UTC
cvs commit: jakarta-struts/doc/userGuide dev_validator.xml
husted 2003/12/11 12:37:47
Modified: doc/userGuide dev_validator.xml
Log:
Update for 1.2.x series.
Revision Changes Path
1.38 +78 -124 jakarta-struts/doc/userGuide/dev_validator.xml
Index: dev_validator.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/dev_validator.xml,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -r1.37 -r1.38
--- dev_validator.xml 9 Sep 2003 17:49:18 -0000 1.37
+++ dev_validator.xml 11 Dec 2003 20:37:47 -0000 1.38
@@ -547,129 +547,74 @@
</section>
-<section href="validator-changes" name="Changes and deprecations">
+<section href="conditionals" name="Conditionally required fields">
<p>
- <strong>New tag attributes.</strong>
- </p>
-
- <p>
- The <a href="struts-html.html#javascript"><html:javascript> tag</a>
- has new attributes defined.
- </p>
-
- <p>
- <strong>Validating against the DTD in the commons-validator.jar.</strong>
- </p>
-
- <p>
- The validator xml files now <strong>validates against the DTD stored
- in the commons-validator.jar </strong>!
- Struts no longer maintains a separate dtd for validator-rules.xml and
- validator.xml.
- Additionally, commons-validator now maintains a unified validator.dtd.
- Change all validator.xml DTD references to:
- </p>
-<pre><![CDATA[
-<!DOCTYPE form-validation PUBLIC
-"-//Apache Software Foundation//DTD Commons Validator Rules Configuration 1.0//EN"
-"http://jakarta.apache.org/commons/dtds/validator_1_0.dtd">
-]]></pre>
-
- <p>
- <strong>Blank fields.</strong>
- </p>
-
- <p>
- The default validator-rules.xml now ignores blank fields for all the
- basic validation types.
- If you require a field to be present then to your applications
- validator.xml field definition add "required" to the depends
- attribute.
- </p>
-
- <p>
- <strong>New range methods.</strong>
- </p>
-
- <p>
- <code>intRange</code> & <code>floatRange</code> methods in both
- JavaScript and Java
- </p>
-
- <p>
- <strong>Conditionally required fields.</strong>
- </p>
-
- <p>
- The most fundamental change is the ability to conditionally require
- validator fields based on the value of other fields.
- It allows you to define logic like "only validate this field if field X is
+ You can define logic like "only validate this field if field X is
non-null and field Y equals 'male'". The recommended way to do this will
be with the <code>validwhen</code> rule, described above, and available
- in the first release after 1.1. The
- <code>requiredif</code> validation rule, which was added in Struts 1.1,
- will be deprecated in favor of this rule, and will be removed in a
+ in the first release after 1.1. The
+ <code>requiredif</code> validation rule, which was added in Struts 1.1,
+ will be deprecated in favor of this rule, and will be removed in a
future release. However, if you are using <code>requiredif</code>, here
is a brief tutorial.
</p>
- <p>Let's assume you have a medical information form with three fields, sex, pregnancyTest, and testResult.
+ <p>Let's assume you have a medical information form with three fields, sex, pregnancyTest, and testResult.
If sex is 'f' or 'F', pregnancyTest is required. If pregnancyTest is not blank, testResult is required.
The entry in your validation.xml file would look like this:
</p>
<pre>
-<form name="medicalStatusForm">
+<![CDATA[
+<form name="medicalStatusForm">
-<field
- property="pregnancyTest" depends="requiredif">
- <arg0 key="medicalStatusForm.pregnancyTest.label"/>
- <var>
- <var-name>field[0]</var-name>
- <var-value>sex</var-value>
- </var>
- <var>
- <var-name>fieldTest[0]</var-name>
- <var-value>EQUAL</var-value>
- </var>
- <var>
- <var-name>fieldValue[0]</var-name>
- <var-value>F</var-value>
- </var>
- <var>
- <var-name>field[1]</var-name>
- <var-value>sex</var-value>
- </var>
- <var>
- <var-name>fieldTest[1]</var-name>
- <var-value>EQUAL</var-value>
- </var>
- <var>
- <var-name>fieldValue[1]</var-name>
- <var-value>f</var-value>
- </var>
- <var>
- <var-name>fieldJoin</var-name>
- <var-value>OR</var-value>
- </var>
-</field>
-
-<field
- property="testResult" depends="requiredif">
- <arg0 key="medicalStatusForm.testResult.label"/>
- <var>
- <var-name>field[0]</var-name>
- <var-value>pregnancyTest</var-value>
- </var>
- <var>
- <var-name>fieldTest[0]</var-name>
- <var-value>NOTNULL</var-value>
- </var>
-</field>
-</form>
-</pre>
-
-
+<field
+ property="pregnancyTest" depends="requiredif">
+ <arg0 key="medicalStatusForm.pregnancyTest.label"/>
+ <var>
+ <var-name>field[0]</var-name>
+ <var-value>sex</var-value>
+ </var>
+ <var>
+ <var-name>fieldTest[0]</var-name>
+ <var-value>EQUAL</var-value>
+ </var>
+ <var>
+ <var-name>fieldValue[0]</var-name>
+ <var-value>F</var-value>
+ </var>
+ <var>
+ <var-name>field[1]</var-name>
+ <var-value>sex</var-value>
+ </var>
+ <var>
+ <var-name>fieldTest[1]</var-name>
+ <var-value>EQUAL</var-value>
+ </var>
+ <var>
+ <var-name>fieldValue[1]</var-name>
+ <var-value>f</var-value>
+ </var>
+ <var>
+ <var-name>fieldJoin</var-name>
+ <var-value>OR</var-value>
+ </var>
+</field>
+
+<field
+ property="testResult" depends="requiredif">
+ <arg0 key="medicalStatusForm.testResult.label"/>
+ <var>
+ <var-name>field[0]</var-name>
+ <var-value>pregnancyTest</var-value>
+ </var>
+ <var>
+ <var-name>fieldTest[0]</var-name>
+ <var-value>NOTNULL</var-value>
+ </var>
+</field>
+</form>
+]]></pre>
<p>
Here's a more complex example using indexed properties.
@@ -801,25 +746,34 @@
the only restriction is that they must all be AND or OR, you can't mix.
</p>
- <p>
- <strong>Deprecations.</strong>
- </p>
-
- <ul>
+</section>
- <li>
- Deprecation of <code>range</code> methods in both JavaScript and Java.
- </li>
+ <section heref="stopOnFirstError" name="Unstoppable JavaScript Validations">
- <li>
- Deprecation of StrutsValidator & StrutsValidatorUtil.
- </li>
+ <p>
+ You can now force the clientside Javascript validation to check all constraints, instead of stopping at the first error. By setting a new property, <code>stopOnFirstError</code>, on the Validator PlugIn to false.
+ </p>
+
+ <p>
+ Here's a sample configuration block that you could use in the struts-config.xml:
+ </p>
+
+ <pre>
+<code>
+<![CDATA[
+ <plug-in className="org.apache.struts.validator.ValidatorPlugIn">
+ <set-property property="pathnames"
+ value="/WEB-INF/validation.xml,/WEB-INF/validator-rules.xml"/>
+ <set-property property="stopOnFirstError" value="true"/>
+ </plug-in>
+ ]]>
- </ul>
+</code>
+</pre>
-</section>
+ </section>
-<section href="tiles" name="Validator API Guide">
+ <section href="api" name="Validator API Guide">
<p>
A concise
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org