husted 2004/01/27 02:32:51
Modified: doc/userGuide building_controller.xml dev_validator.xml
Log:
Add some [Since Struts 1.2.0] notations, per #26405, as suggested by Ralf Hauser.
Revision Changes Path
1.76 +1 -1 jakarta-struts/doc/userGuide/building_controller.xml
Index: building_controller.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/userGuide/building_controller.xml,v
retrieving revision 1.75
retrieving revision 1.76
diff -u -r1.75 -r1.76
--- building_controller.xml 31 Dec 2003 01:09:13 -0000 1.75
+++ building_controller.xml 27 Jan 2004 10:32:50 -0000 1.76
@@ -1370,7 +1370,7 @@
<section name="4.10 Using Wildcards in ActionMappings"
href="action_mapping_wildcards">
<p>
- As a Struts application grows in size, so will the number of action
+ [Since Struts 1.2.0] As a Struts application grows in size, so will the number
of action
mappings. Wildcards can be used to combine similiar mappings into one
more generic mapping.
</p>
1.42 +3 -3 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.41
retrieving revision 1.42
diff -u -r1.41 -r1.42
--- dev_validator.xml 17 Jan 2004 03:32:11 -0000 1.41
+++ dev_validator.xml 27 Jan 2004 10:32:51 -0000 1.42
@@ -402,7 +402,7 @@
<section href="validwhen" name="Designing Complex Validations with validwhen">
<p>
- A frequent requirement in validation design is to validate one field
+ [Since Struts 1.2.0] A frequent requirement in validation design is to validate
one field
against another (for example, if you have asked the user to type in
a password twice for confirmation, to make sure that the values match.)
In addition, there are fields in a form that may only be required if
@@ -927,10 +927,10 @@
</section>
- <section heref="stopOnFirstError" name="Unstoppable JavaScript Validations">
+ <section href="stopOnFirstError" name="Unstoppable JavaScript Validations">
<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.
+ [Since Struts 1.2.0] You can 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>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
