cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2004-01-16 Thread husted
husted  2004/01/16 19:32:11

  Modified:doc/userGuide dev_validator.xml
  Log:
  Apply #26209 Validator User Guide: New Section Listing Standard Validations 
submitted by Niall Pemberton.
  
  Revision  ChangesPath
  1.41  +179 -0jakarta-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.40
  retrieving revision 1.41
  diff -u -r1.40 -r1.41
  --- dev_validator.xml 2 Jan 2004 11:55:38 -   1.40
  +++ dev_validator.xml 17 Jan 2004 03:32:11 -  1.41
  @@ -9,6 +9,7 @@
 authorDavid Winterfeldt/author
 authorJames Turner/author
 authorRob Leland/author
  +  authorNiall Pemberton/author
   titleThe Struts User's Guide - Validator Guide/title
   /properties
   
  @@ -153,6 +154,184 @@
   ]]/code/pre
   
   /section
  +
  +section href=builtin name=Standard Built In Validations
  +
  +p
  +Validator is shipped with the following set of pre-defined validation rules.
  +/p
  +ul
  +  listrongrequired/strong - mandatory field validation. Has no 
variables.
  +precode![CDATA[
  +field property=name depends=required
  +arg0 key=customer.name/
  +/field
  +]]/code/pre
  +  /li
  +  listrongrequiredif/strong - field dependant validator
  +  preDeprecated, use validwhen./pre
  +  /li
  +  listrongvalidwhen/strong - validator for checking one field 
against another.
  +  presee later section titled strongDesigning Complex 
Validations with validwhen/strong./pre
  +  /li
  +  listrongminlength/strong - validate input data isn't less than 
a specified minimum length.
  +  Requires a codeminlength/code variable.
  +precode![CDATA[
  +field property=name depends=required,minlength
  +arg0 key=customer.name/
  +arg1 name=minlength key=${var:minlength} resource=false/
  +varvar-nameminlength/var-namevar-value3/var-value/var
  +/field
  +]]/code/pre
  +  /li
  +  listrongmaxlength/strong - validate input data doesn't exceed a 
specified maximum length.
  +  Requires a codemaxlength/code variable.
  +precode![CDATA[
  +field property=name depends=required,maxlength
  +arg0 key=customer.name/
  +arg1 name=maxlength key=${var:maxlength} resource=false/
  +varvar-namemaxlength/var-namevar-value30/var-value/var
  +/field
  +]]/code/pre
  +  /li
  +  listrongmask/strong - validate format according to a regular 
expression.
  +  Requires a codemask/code variable to specify the regular 
expression.
  +  Since version 1.1, the regular expression must start
  +  with a code^/code and end with a code$/code (see example 
below).
  +precode![CDATA[
  +field property=name depends=required,mask
  +msg name=mask key=registrationForm.lastname.maskmsg/
  +arg0 key=registration.name/
  +varvar-namemask/var-namevar-value^[a-zA-Z]*$/var-value/var
  +/field
  +]]/code/pre
  +  /li
  +  listrongbyte/strong - validates that a field can be converted 
to a Byte.
  +precode![CDATA[
  +field property=age depends=byte
  +arg0 key=employee.age/
  +/field
  +]]/code/pre
  +  /li
  +  listrongshort/strong - validates that a field can be converted 
to a Short.
  +precode![CDATA[
  +field property=productnumber depends=short
  +arg0 key=order.prodno/
  +/field
  +]]/code/pre
  +  /li
  +  listronginteger/strong - validates that a field can be 
converted to an Integer.
  +precode![CDATA[
  +field property=ordernumber depends=integer
  +arg0 key=order.number/
  +/field
  +]]/code/pre
  +  /li
  +  listronglong/strong - validates that a field can be converted 
to a Long.
  +precode![CDATA[
  +field property=ordernumber depends=long
  +arg0 key=order.number/
  +/field
  +]]/code/pre
  +  /li
  +  listrongfloat/strong - validates that a field can be converted 
to a Float.
  +precode![CDATA[
  +field property=amount depends=float
  +arg0 key=sale.amount/
  +/field
  +]]/code/pre
  +  /li
  +  listrongdouble/strong - validates that a field can be converted 
to a Double.
  +precode![CDATA[
  +field property=amount depends=double
  +arg0 key=sale.amount/
  +/field
  +]]/code/pre
  +  /li
  +  listrongdate/strong - validates that a field can be converted 
to a Date.
  +  This validation rule uses 

cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2004-01-01 Thread husted
husted  2004/01/01 08:46:29

  Modified:doc/userGuide dev_validator.xml
  Log:
  Fix name value, per #25850 (Dasa Paddock)
  
  Revision  ChangesPath
  1.39  +4 -4  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.38
  retrieving revision 1.39
  diff -u -r1.38 -r1.39
  --- dev_validator.xml 11 Dec 2003 20:37:47 -  1.38
  +++ dev_validator.xml 1 Jan 2004 16:46:28 -   1.39
  @@ -134,11 +134,11 @@
   depends=required,integer,intRange
   arg0 key=typeForm.integer.displayname/
   arg1
  -name=range
  +name=intRange
   key=${var:min}
   resource=false/
   arg2
  -name=range
  +name=intRange
   key=${var:max}
   resource=false/
   var
  @@ -201,11 +201,11 @@
   depends=required,integer,intRange
   arg0 key=typeForm.integer.displayname/
   arg1
  -name=range
  +name=intRange
   key=${var:min}
   resource=false/
   arg2
  -name=range
  +name=intRange
   key=${var:max}
   resource=false/
   var
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2003-12-11 Thread husted
husted  2003/12/11 12:37:47

  Modified:doc/userGuide dev_validator.xml
  Log:
  Update for 1.2.x series.
  
  Revision  ChangesPath
  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 -   1.37
  +++ dev_validator.xml 11 Dec 2003 20:37:47 -  1.38
  @@ -547,129 +547,74 @@
   
   /section
   
  -section href=validator-changes name=Changes and deprecations
  +section href=conditionals name=Conditionally required fields
   
   p
  -strongNew tag attributes./strong
  -/p
  -
  -p
  -The a href=struts-html.html#javascriptlt;html:javascriptgt; tag/a
  -has new attributes defined.
  -/p
  -
  -p
  -strongValidating against the DTD in the commons-validator.jar./strong
  -/p
  -
  -p
  -The validator xml files now strongvalidates 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
  -strongBlank 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
  -strongNew range methods./strong
  -/p
  -
  -p
  -codeintRange/code amp; codefloatRange/code methods in both
  -JavaScript and Java
  -/p
  -
  -p
  -strongConditionally 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 codevalidwhen/code rule, described above, and available
  -in the first release after 1.1.  The 
  -coderequiredif/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
  +coderequiredif/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 coderequiredif/code, here
   is a brief tutorial.
   /p
   
  - pLet's assume you have a medical information form with three fields, sex, 
pregnancyTest, and testResult.  
  + pLet'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
  -lt;form name=medicalStatusFormgt;
  +![CDATA[
  +form name=medicalStatusForm
   
  -lt;field
  -property=pregnancyTest depends=requiredifgt;
  -  lt;arg0 key=medicalStatusForm.pregnancyTest.label/gt;
  -  lt;vargt;
  -lt;var-namegt;field[0]lt;/var-namegt;
  -lt;var-valuegt;sexlt;/var-valuegt;
  -  lt;/vargt;
  -  lt;vargt;
  -lt;var-namegt;fieldTest[0]lt;/var-namegt;
  -lt;var-valuegt;EQUALlt;/var-valuegt;
  -  lt;/vargt;
  -  lt;vargt;
  -lt;var-namegt;fieldValue[0]lt;/var-namegt;
  -lt;var-valuegt;Flt;/var-valuegt;
  -  lt;/vargt;
  -  lt;vargt;
  -lt;var-namegt;field[1]lt;/var-namegt;
  -lt;var-valuegt;sexlt;/var-valuegt;
  -  lt;/vargt;
  -  lt;vargt;
  -lt;var-namegt;fieldTest[1]lt;/var-namegt;
  -lt;var-valuegt;EQUALlt;/var-valuegt;
  -  lt;/vargt;
  -  lt;vargt;
  -lt;var-namegt;fieldValue[1]lt;/var-namegt;
  -lt;var-valuegt;flt;/var-valuegt;
  -  lt;/vargt;
  -  lt;vargt;
  -lt;var-namegt;fieldJoinlt;/var-namegt;
  -lt;var-valuegt;ORlt;/var-valuegt;
  -  lt;/vargt;
  -lt;/fieldgt;
  -
  -lt;field
  -property=testResult depends=requiredifgt;
  -  lt;arg0 key=medicalStatusForm.testResult.label/gt;
  -  lt;vargt;
  -lt;var-namegt;field[0]lt;/var-namegt;
  -lt;var-valuegt;pregnancyTestlt;/var-valuegt;
  -  lt;/vargt;
  -  lt;vargt;
  -

cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2003-03-20 Thread turner
turner  2003/03/20 08:36:35

  Modified:doc/faqs newbie.xml
   doc/userGuide dev_validator.xml
  Log:
  Added simpler example of using the requiredif validator test to dev_validator.xml,
  added faq on using requiredif to newbie.xml, also fixed syntax of more complicated
  example in dev_validator.xml to actually be correct (it was using things like
  fieldJoin instead of field-join.
  
  Revision  ChangesPath
  1.13  +63 -0 jakarta-struts/doc/faqs/newbie.xml
  
  Index: newbie.xml
  ===
  RCS file: /home/cvs/jakarta-struts/doc/faqs/newbie.xml,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- newbie.xml5 Feb 2003 04:23:20 -   1.12
  +++ newbie.xml20 Mar 2003 16:36:34 -  1.13
  @@ -5,6 +5,7 @@
   authorJames Holmes/author
   authorCraig R. McClanahan/author
   authorEdgar Dollin/author
  +authorJames Turner/author
   titleNewbie FAQ - Apache Struts/title
   /properties
   body
  @@ -110,6 +111,10 @@
   a href=#prepopulateHow can I prepopulate a form?/a
   /li
   
  +li
  +a href=#requiredifCan you give me a simple example of using the requiredif 
Validator rule?/a
  +/li
  +
   /ul

   p
  @@ -699,6 +704,64 @@
   instead of calling your processing action./li
   /ul
   
  +/section
  +
  +section href=requiredif
  + name=Can you give me a simple example of using the requiredif Validator 
rule?
  + pLet's assume you have a medical information form with three fields, sex, 
dateOfLastMamogram, and testResult.  
  + If sex is 'f' or 'F', dateOfLastMamogram is required.  If dateOfLastMamogram 
is not blank, testResult is required.
  + The entry in your validation.xml file would look like this:
  + /p
  + pre
  +lt;form name=medicalStatusFormgt;
  +
  +lt;field
  +property=dateOfLastMamogram depends=requiredifgt;
  +  lt;arg0 key=medicalStatusForm.dateOfLastMamogram.label/gt;
  +  lt;vargt;
  +lt;var-namegt;field[0]lt;/var-namegt;
  +lt;var-valuegt;sexlt;/var-valuegt;
  +  lt;/vargt;
  +  lt;vargt;
  +lt;var-namegt;field-test[0]lt;/var-namegt;
  +lt;var-valuegt;EQUALlt;/var-valuegt;
  +  lt;/vargt;
  +  lt;vargt;
  +lt;var-namegt;field-value[0]lt;/var-namegt;
  +lt;var-valuegt;Flt;/var-valuegt;
  +  lt;/vargt;
  +  lt;vargt;
  +lt;var-namegt;field[1]lt;/var-namegt;
  +lt;var-valuegt;sexlt;/var-valuegt;
  +  lt;/vargt;
  +  lt;vargt;
  +lt;var-namegt;field-test[1]lt;/var-namegt;
  +lt;var-valuegt;EQUALlt;/var-valuegt;
  +  lt;/vargt;
  +  lt;vargt;
  +lt;var-namegt;field-value[1]lt;/var-namegt;
  +lt;var-valuegt;flt;/var-valuegt;
  +  lt;/vargt;
  +  lt;vargt;
  +lt;var-namegt;field-joinlt;/var-namegt;
  +lt;var-valuegt;ORlt;/var-valuegt;
  +  lt;/vargt;
  +lt;/fieldgt;
  +
  +lt;field
  +property=testResult depends=requiredifgt;
  +  lt;arg0 key=medicalStatusForm.testResult.label/gt;
  +  lt;vargt;
  +lt;var-namegt;field[0]lt;/var-namegt;
  +lt;var-valuegt;dateOfLastMamogramlt;/var-valuegt;
  +  lt;/vargt;
  +  lt;vargt;
  +lt;var-namegt;field-test[0]lt;/var-namegt;
  +lt;var-valuegt;NOTNULLlt;/var-valuegt;
  +  lt;/vargt;
  +lt;/fieldgt;
  +lt;/formgt;
  +/pre
   /section
   
   
  
  
  
  1.30  +68 -12jakarta-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.29
  retrieving revision 1.30
  diff -u -r1.29 -r1.30
  --- dev_validator.xml 19 Mar 2003 04:49:04 -  1.29
  +++ dev_validator.xml 20 Mar 2003 16:36:34 -  1.30
  @@ -502,8 +502,65 @@
   non-null and field Y equals 'male'.
   /p
   
  + pLet's assume you have a medical information form with three fields, sex, 
dateOfLastMamogram, and testResult.  
  + If sex is 'f' or 'F', dateOfLastMamogram is required.  If dateOfLastMamogram 
is not blank, testResult is required.
  + The entry in your validation.xml file would look like this:
  + /p
  + pre
  +lt;form name=medicalStatusFormgt;
  +
  +lt;field
  +property=dateOfLastMamogram depends=requiredifgt;
  +  lt;arg0 key=medicalStatusForm.dateOfLastMamogram.label/gt;
  +  lt;vargt;
  +lt;var-namegt;field[0]lt;/var-namegt;
  +lt;var-valuegt;sexlt;/var-valuegt;
  +  lt;/vargt;
  +  lt;vargt;
  +lt;var-namegt;field-test[0]lt;/var-namegt;
  +lt;var-valuegt;EQUALlt;/var-valuegt;
  +  lt;/vargt;
  +  lt;vargt;
  +lt;var-namegt;field-value[0]lt;/var-namegt;
  +lt;var-valuegt;Flt;/var-valuegt;
  +  lt;/vargt;
  +  lt;vargt;
  +lt;var-namegt;field[1]lt;/var-namegt;
  +lt;var-valuegt;sexlt;/var-valuegt;
  +  lt;/vargt;
  +  lt;vargt;
  +lt;var-namegt;field-test[1]lt;/var-namegt;
  +lt;var-valuegt;EQUALlt;/var-valuegt;
  +  lt;/vargt;
  +  

cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2003-03-20 Thread turner
turner  2003/03/20 08:42:12

  Modified:doc/faqs newbie.xml
   doc/userGuide dev_validator.xml
  Log:
  Fixed new examples to use camelCase as per nightly build change made by
  David Graham, and changed examples because discussing female anatomy
  evidently made him blush :-)
  
  Revision  ChangesPath
  1.14  +11 -11jakarta-struts/doc/faqs/newbie.xml
  
  Index: newbie.xml
  ===
  RCS file: /home/cvs/jakarta-struts/doc/faqs/newbie.xml,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- newbie.xml20 Mar 2003 16:36:34 -  1.13
  +++ newbie.xml20 Mar 2003 16:42:11 -  1.14
  @@ -708,26 +708,26 @@
   
   section href=requiredif
name=Can you give me a simple example of using the requiredif Validator 
rule?
  - pLet's assume you have a medical information form with three fields, sex, 
dateOfLastMamogram, and testResult.  
  - If sex is 'f' or 'F', dateOfLastMamogram is required.  If dateOfLastMamogram 
is not blank, testResult is required.
  + pLet'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
   lt;form name=medicalStatusFormgt;
   
   lt;field
  -property=dateOfLastMamogram depends=requiredifgt;
  -  lt;arg0 key=medicalStatusForm.dateOfLastMamogram.label/gt;
  +property=pregnancyTest depends=requiredifgt;
  +  lt;arg0 key=medicalStatusForm.pregnancyTest.label/gt;
 lt;vargt;
   lt;var-namegt;field[0]lt;/var-namegt;
   lt;var-valuegt;sexlt;/var-valuegt;
 lt;/vargt;
 lt;vargt;
  -lt;var-namegt;field-test[0]lt;/var-namegt;
  +lt;var-namegt;fieldTest[0]lt;/var-namegt;
   lt;var-valuegt;EQUALlt;/var-valuegt;
 lt;/vargt;
 lt;vargt;
  -lt;var-namegt;field-value[0]lt;/var-namegt;
  +lt;var-namegt;fieldValue[0]lt;/var-namegt;
   lt;var-valuegt;Flt;/var-valuegt;
 lt;/vargt;
 lt;vargt;
  @@ -735,15 +735,15 @@
   lt;var-valuegt;sexlt;/var-valuegt;
 lt;/vargt;
 lt;vargt;
  -lt;var-namegt;field-test[1]lt;/var-namegt;
  +lt;var-namegt;fieldTest[1]lt;/var-namegt;
   lt;var-valuegt;EQUALlt;/var-valuegt;
 lt;/vargt;
 lt;vargt;
  -lt;var-namegt;field-value[1]lt;/var-namegt;
  +lt;var-namegt;fieldValue[1]lt;/var-namegt;
   lt;var-valuegt;flt;/var-valuegt;
 lt;/vargt;
 lt;vargt;
  -lt;var-namegt;field-joinlt;/var-namegt;
  +lt;var-namegt;fieldJoinlt;/var-namegt;
   lt;var-valuegt;ORlt;/var-valuegt;
 lt;/vargt;
   lt;/fieldgt;
  @@ -753,10 +753,10 @@
 lt;arg0 key=medicalStatusForm.testResult.label/gt;
 lt;vargt;
   lt;var-namegt;field[0]lt;/var-namegt;
  -lt;var-valuegt;dateOfLastMamogramlt;/var-valuegt;
  +lt;var-valuegt;pregnancyTestlt;/var-valuegt;
 lt;/vargt;
 lt;vargt;
  -lt;var-namegt;field-test[0]lt;/var-namegt;
  +lt;var-namegt;fieldTest[0]lt;/var-namegt;
   lt;var-valuegt;NOTNULLlt;/var-valuegt;
 lt;/vargt;
   lt;/fieldgt;
  
  
  
  1.31  +20 -20jakarta-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.30
  retrieving revision 1.31
  diff -u -r1.30 -r1.31
  --- dev_validator.xml 20 Mar 2003 16:36:34 -  1.30
  +++ dev_validator.xml 20 Mar 2003 16:42:11 -  1.31
  @@ -502,26 +502,26 @@
   non-null and field Y equals 'male'.
   /p
   
  - pLet's assume you have a medical information form with three fields, sex, 
dateOfLastMamogram, and testResult.  
  - If sex is 'f' or 'F', dateOfLastMamogram is required.  If dateOfLastMamogram 
is not blank, testResult is required.
  + pLet'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
   lt;form name=medicalStatusFormgt;
   
   lt;field
  -property=dateOfLastMamogram depends=requiredifgt;
  -  lt;arg0 key=medicalStatusForm.dateOfLastMamogram.label/gt;
  +property=pregnancyTest depends=requiredifgt;
  +  lt;arg0 key=medicalStatusForm.pregnancyTest.label/gt;
 lt;vargt;
   lt;var-namegt;field[0]lt;/var-namegt;
   lt;var-valuegt;sexlt;/var-valuegt;
 lt;/vargt;
 lt;vargt;
  -lt;var-namegt;field-test[0]lt;/var-namegt;
  +lt;var-namegt;fieldTest[0]lt;/var-namegt;
   lt;var-valuegt;EQUALlt;/var-valuegt;
 lt;/vargt;
 lt;vargt;
  -

Re: cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2003-03-20 Thread David Graham
  Modified:doc/faqs newbie.xml
   doc/userGuide dev_validator.xml
  Log:
  Fixed new examples to use camelCase as per nightly build change made by
  David Graham, and changed examples because discussing female anatomy
  evidently made him blush :-)
Thanks for saving this to CVS for a permanent reminder :-).

David

_
Add photos to your messages with MSN 8. Get 2 months FREE*.  
http://join.msn.com/?page=features/featuredemail

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2003-03-20 Thread James Mitchell
On Thu, 2003-03-20 at 11:45, David Graham wrote:
Modified:doc/faqs newbie.xml
 doc/userGuide dev_validator.xml
Log:
Fixed new examples to use camelCase as per nightly build change made by
David Graham, and changed examples because discussing female anatomy
evidently made him blush :-)
 
 Thanks for saving this to CVS for a permanent reminder :-).

LOL!!!

 
 David
 
 
 _
 Add photos to your messages with MSN 8. Get 2 months FREE*.  
 http://join.msn.com/?page=features/featuredemail
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
-- 
James Mitchell
Software Developer/Struts Evangelist
http://www.open-tools.org




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2003-03-18 Thread dgraham
dgraham 2003/03/18 20:49:04

  Modified:doc/userGuide dev_validator.xml
  Log:
  Remove duplicate example.
  
  Revision  ChangesPath
  1.29  +0 -15 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.28
  retrieving revision 1.29
  diff -u -r1.28 -r1.29
  --- dev_validator.xml 16 Mar 2003 16:30:14 -  1.28
  +++ dev_validator.xml 19 Mar 2003 04:49:04 -  1.29
  @@ -91,21 +91,6 @@
   validator's name attribute.
   /p
   
  -precode![CDATA[
  -field
  -property=lastName
  -depends=required,mask
  -msg
  -name=mask
  -key=registrationForm.lastname.maskmsg/
  -arg0 key=registrationForm.lastname.displayname/
  -var
  -var-namemask/var-name
  -var-value^[a-zA-Z]*$/var-value
  -/var
  -/field
  -]]/code/pre
  -
   p
   The arguments for error messages can be set with the arg0-arg3 elements.
   If the arg0-arg3 elements' name attribute isn't set, it will become the
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2003-03-16 Thread husted
husted  2003/03/16 08:25:55

  Modified:doc/userGuide dev_validator.xml
  Log:
  Update per ticket #17493 by Matt Raible.
  
  Revision  ChangesPath
  1.27  +6 -0  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.26
  retrieving revision 1.27
  diff -u -r1.26 -r1.27
  --- dev_validator.xml 15 Mar 2003 22:32:20 -  1.26
  +++ dev_validator.xml 16 Mar 2003 16:25:55 -  1.27
  @@ -91,6 +91,12 @@
   validator's name attribute.
   /p
   
  +p
  +For an example of creating atwofields validator, see
  +a href=http://tinyurl.com/6jnv;Struts Validator: Validating Two Fields 
Match/a
  +by Matt Raible.
  +/p
  +
   precode![CDATA[
   field
   property=lastName
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2003-03-15 Thread dgraham
dgraham 2003/03/15 14:32:20

  Modified:doc/userGuide dev_validator.xml
  Log:
  Fixed field_test to fieldTest for documentation.
  
  Revision  ChangesPath
  1.26  +1 -1  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.25
  retrieving revision 1.26
  diff -u -r1.25 -r1.26
  --- dev_validator.xml 15 Mar 2003 22:27:44 -  1.25
  +++ dev_validator.xml 15 Mar 2003 22:32:20 -  1.26
  @@ -566,7 +566,7 @@
   var-valuetrue/var-value
 /var
 var
  -var-namefield_test[0]/var-name
  +var-namefieldTest[0]/var-name
   var-valueNOTNULL/var-value
 /var
   /field
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2003-03-12 Thread dgraham
dgraham 2003/03/12 17:59:40

  Modified:doc/userGuide dev_validator.xml
  Log:
  Added note about requiring a default formset before i18n formsets.
  
  Revision  ChangesPath
  1.24  +7 -2  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.23
  retrieving revision 1.24
  diff -u -r1.23 -r1.24
  --- dev_validator.xml 5 Mar 2003 01:15:27 -   1.23
  +++ dev_validator.xml 13 Mar 2003 01:59:39 -  1.24
  @@ -71,10 +71,15 @@
   correspond with the codejava.util.Locale/code class.
   If they are not used, the codeFormSet/code  will be set to the default
   locale.
  -A codeFormSet/code  can also have constants associated with it.
  -On the same level as a codeFormSet/code  there can be a global element
  +A codeFormSet/code can also have constants associated with it.
  +On the same level as a codeFormSet/code there can be a global element
   which can also have constants and have validator actions that perform
   validations.
  +/p
  +p
  +strongNote/strong: You must declare a default codeFormSet/code without 
  +internationalization before your internationalized codeFormSet/codes.  This
  +allows the Validator to fall back to the default version if no locale is found.
   /p
   
   p
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2003-03-04 Thread dgraham
dgraham 2003/03/04 17:15:28

  Modified:doc/userGuide dev_validator.xml
  Log:
  Minor typo corrections.
  
  Revision  ChangesPath
  1.23  +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.22
  retrieving revision 1.23
  diff -u -r1.22 -r1.23
  --- dev_validator.xml 15 Feb 2003 03:17:07 -  1.22
  +++ dev_validator.xml 5 Mar 2003 01:15:27 -   1.23
  @@ -251,7 +251,7 @@
   
   p
   If the a href=struts-html.html#javascriptJavascript Tag/a is used,
  -the client side Javascript  eneration looks for a value in the validator's
  +the client side Javascript generation looks for a value in the validator's
   javascript attribute and generates an object that the supplied method can
   use to validate the form.
   For a more detailed explanation of how the Javascript Validator Tag works,
  @@ -341,9 +341,9 @@
   p
   The field element has an optional page attribute.
   It can be set to an integer.
  -All validation for the any field page value less than or equal to the
  +All validation for any field on a page less than or equal to the
   current page is performed server side.
  -All validation for the any field page equal to the current page is
  +All validation for any field on a page equal to the current page is
   generated for the client side Javascript.
   A mutli-part form expects the page attribute to be set.
   /p
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2003-02-14 Thread dgraham
dgraham 2003/02/14 19:17:07

  Modified:doc/userGuide dev_validator.xml
  Log:
  Fixed constant usage example for PR# 17018.
  
  Revision  ChangesPath
  1.22  +4 -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.21
  retrieving revision 1.22
  diff -u -r1.21 -r1.22
  --- dev_validator.xml 8 Feb 2003 00:35:28 -   1.21
  +++ dev_validator.xml 15 Feb 2003 03:17:07 -  1.22
  @@ -181,9 +181,10 @@
   
   precode![CDATA[
   global
  -constant
  -name=zip
  -value=^\d{5}(-\d{4})?$ /
  +constant
  +constant-namezip/constant-name
  +constant-value^\d{5}(-\d{4})?$/constant-value
  +/constant
   /global
   
   field
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2003-02-07 Thread turner
turner  2003/02/07 16:35:28

  Modified:doc/userGuide dev_validator.xml
  Log:
  Document issue raised in pr 16609.
  
  Will fix bug in 1.2
  
  Revision  ChangesPath
  1.21  +6 -0  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.20
  retrieving revision 1.21
  diff -u -r1.20 -r1.21
  --- dev_validator.xml 19 Jan 2003 00:40:41 -  1.20
  +++ dev_validator.xml 8 Feb 2003 00:35:28 -   1.21
  @@ -131,6 +131,12 @@
   If the resource attribute is set to false, it will pass in the value directly
   without retrieving the value from the message resources.
   /p
  +p
  +Note that as of the Struts 1.1 release, you must explicitly define your message
  +resource in any module that is going to use the Validator, due to a problem
  +accessing the top-level resource.  This only effects applications which are
  +using modules.
  +/p
   
   precode![CDATA[
   field
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2002-12-27 Thread husted
husted  2002/12/27 01:53:39

  Modified:doc/userGuide dev_validator.xml
  Log:
  Conform line-length. No content changes.
  
  Revision  ChangesPath
  1.17  +236 -171  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.16
  retrieving revision 1.17
  diff -u -r1.16 -r1.17
  --- dev_validator.xml 24 Dec 2002 01:50:07 -  1.16
  +++ dev_validator.xml 27 Dec 2002 09:53:39 -  1.17
  @@ -1,13 +1,20 @@
   ?xml version=1.0 encoding=ISO-8859-1?
   document url=./resources.xml
  +
  +!--
  +//  78
  +--
  +
   properties
 authorDavid Winterfeldt/author 
 authorJames Turner/author 
 authorRob Leland/author 
   titleThe Struts User's Guide - Validator Guide/title
   /properties
  -body 
  -chapter name=Struts Validator Guide 
  +
  +body
  +
  +chapter name=Struts Validator Guide
   
   section href=validator name=Struts Validator
   
  @@ -17,219 +24,277 @@
   
   p
   Cover basic functionality as documented on David's web site.
  -a href=http://home.earthlink.net/~dwinterfeldt/;Validation Framework for Struts 
/a 
  +a href=http://home.earthlink.net/~dwinterfeldt/;Validation Framework for 
  +Struts /a 
   /p
   
   p
  -Changes in the validator behavior and deprecation of functionality from original 
validator
  +Changes in the validator behavior and deprecation of functionality from 
  +original validator
   /p
  +
   ul
  -li
  -  The validator xml files now strongvalidates against the DTD stored in the 
commons-validator.jar /strong!
  -/li
  -li
  -  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.
  -/li
  -li
  -  The Javascript Tag has new attributes defined.
  -/li
  -li
  -  Deprecation of range() methods in both JavaScript and Java
  -/li
  -li
  -  Deprecation of StrutsValidator amp; StrutsValidatorUtil
  -/li
  +
  +li
  +The validator xml files now strongvalidates against the DTD stored in the 
  +commons-validator.jar /strong!
  +/li
  +
  +li
  +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.
  +/li
  +
  +li
  +The Javascript Tag has new attributes defined.
  +/li
  +
  +li
  +Deprecation of coderange/code methods in both JavaScript and Java
  +/li
  +
  +li
  +Deprecation of StrutsValidator amp; StrutsValidatorUtil
  +/li
  +
   /ul
  +
   p
   Struts 1.1 has also added additional functionality over the original validator
   contributed by David Winterfeldt.
   /p
   
   ul
  +
   li
  -  Conditionally required fields
  +Conditionally required fields
   /li
  +
   li
  -  intRange() amp; floatRange() methods in both JavaScript and Java
  +codeintRange/code amp; codefloatRange/code methods in both JavaScript 
  +and Java
   /li
  +
   /ul
  +
   /section
  +
   section href=validator-bugs name=Known Bugs
  -p Current know bugs can be found by clicking:
  -a 
href=http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMEDamp;bug_status=NEWamp;bug_status=ASSIGNEDamp;bug_status=REOPENEDamp;bug_status=VERIFIEDamp;bug_severity=Blockeramp;bug_severity=Criticalamp;bug_severity=Majoramp;bug_severity=Normalamp;bug_severity=Minoramp;email1=amp;emailtype1=substringamp;emailassigned_to1=1amp;email2=amp;emailtype2=substringamp;emailreporter2=1amp;bugidtype=includeamp;bug_id=amp;changedin=amp;votes=amp;chfieldfrom=amp;chfieldto=Nowamp;chfieldvalue=amp;product=Strutsamp;version=1.1+Beta+1amp;version=1.1+Beta+2amp;version=Nightly+Buildamp;version=Unknownamp;component=Validator+Frameworkamp;short_desc=amp;short_desc_type=allwordssubstramp;long_desc=amp;long_desc_type=allwordssubstramp;bug_file_loc=amp;bug_file_loc_type=allwordssubstramp;keywords=amp;keywords_type=anywordsamp;field0-0-0=noopamp;type0-0-0=noopamp;value0-0-0=amp;cmdtype=doitamp;newqueryname=amp;order=Reuse+same+sort+as+last+time;
  -Validation Bugs/a /p
  -pSince validation also relies on the commons-validator those bugs can be found
  -a 

cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2002-12-27 Thread husted
husted  2002/12/27 02:24:06

  Modified:doc/userGuide dev_validator.xml
  Log:
  Minor structural changes to existing content.
  
  Revision  ChangesPath
  1.18  +114 -82   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.17
  retrieving revision 1.18
  diff -u -r1.17 -r1.18
  --- dev_validator.xml 27 Dec 2002 09:53:39 -  1.17
  +++ dev_validator.xml 27 Dec 2002 10:24:05 -  1.18
  @@ -6,9 +6,9 @@
   --
   
   properties
  -  authorDavid Winterfeldt/author 
  -  authorJames Turner/author 
  -  authorRob Leland/author 
  +  authorDavid Winterfeldt/author
  +  authorJames Turner/author
  +  authorRob Leland/author
   titleThe Struts User's Guide - Validator Guide/title
   /properties
   
  @@ -18,48 +18,32 @@
   
   section href=validator name=Struts Validator
   
  -p
  -[:TODO:]
  -/p
  +p
  +The Struts Validator, in some form, has been available since the
  +days of Struts 0.5.
  +It was orignally packaged as a developer contribution.
  +Later, the core code was moved to the Jakarta Commons and
  +a Struts specific extension became part of Struts 1.1.
  +/p
   
  -p
  -Cover basic functionality as documented on David's web site.
  -a href=http://home.earthlink.net/~dwinterfeldt/;Validation Framework for 
  -Struts /a 
  -/p
  +p
  +For the convenience of the many developers who have been using
  +the Struts Validator all along, this document first overviews
  +the core functionality and then covers the changes and
  +new functionality added in the Struts 1.1.
  +/p
  +
  +p
  +[:TODO: Cover basic functionality as documented on David's web site.
  +a href=http://home.earthlink.net/~dwinterfeldt/;Validation Framework for
  +Struts /a]
  +/p
   
   p
  -Changes in the validator behavior and deprecation of functionality from 
  +Changes in the validator behavior and deprecation of functionality from
   original validator
   /p
   
  -ul
  -
  -li
  -The validator xml files now strongvalidates against the DTD stored in the 
  -commons-validator.jar /strong!
  -/li
  -
  -li
  -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.
  -/li
  -
  -li
  -The Javascript Tag has new attributes defined.
  -/li
  -
  -li
  -Deprecation of coderange/code methods in both JavaScript and Java
  -/li
  -
  -li
  -Deprecation of StrutsValidator amp; StrutsValidatorUtil
  -/li
  -
  -/ul
   
   p
   Struts 1.1 has also added additional functionality over the original validator
  @@ -73,7 +57,7 @@
   /li
   
   li
  -codeintRange/code amp; codefloatRange/code methods in both JavaScript 
  +codeintRange/code amp; codefloatRange/code methods in both JavaScript
   and Java
   /li
   
  @@ -84,17 +68,25 @@
   section href=validator-bugs name=Known Bugs
   
   p
  -Current know bugs can be found by clicking:
  -a 
href=http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMEDamp;bug_status=NEWamp;bug_status=ASSIGNEDamp;bug_status=REOPENEDamp;bug_status=VERIFIEDamp;bug_severity=Blockeramp;bug_severity=Criticalamp;bug_severity=Majoramp;bug_severity=Normalamp;bug_severity=Minoramp;email1=amp;emailtype1=substringamp;emailassigned_to1=1amp;email2=amp;emailtype2=substringamp;emailreporter2=1amp;bugidtype=includeamp;bug_id=amp;changedin=amp;votes=amp;chfieldfrom=amp;chfieldto=Nowamp;chfieldvalue=amp;product=Strutsamp;version=1.1+Beta+1amp;version=1.1+Beta+2amp;version=Nightly+Buildamp;version=Unknownamp;component=Validator+Frameworkamp;short_desc=amp;short_desc_type=allwordssubstramp;long_desc=amp;long_desc_type=allwordssubstramp;bug_file_loc=amp;bug_file_loc_type=allwordssubstramp;keywords=amp;keywords_type=anywordsamp;field0-0-0=noopamp;type0-0-0=noopamp;value0-0-0=amp;cmdtype=doitamp;newqueryname=amp;order=Reuse+same+sort+as+last+time;
  -Validation Bugs/a
  -/p
  -
  -p
  -Since validation also relies on the commons-validator those bugs can be found
  -a 

cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2002-12-27 Thread husted
husted  2002/12/27 03:15:06

  Modified:doc/userGuide dev_validator.xml
  Log:
  Port David's overview -- these sections need to be reviewed in the context of the 
current codebase.
  
  Revision  ChangesPath
  1.19  +401 -43   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.18
  retrieving revision 1.19
  diff -u -r1.18 -r1.19
  --- dev_validator.xml 27 Dec 2002 10:24:05 -  1.18
  +++ dev_validator.xml 27 Dec 2002 11:15:06 -  1.19
  @@ -34,34 +34,387 @@
   /p
   
   p
  -[:TODO: Cover basic functionality as documented on David's web site.
  -a href=http://home.earthlink.net/~dwinterfeldt/;Validation Framework for
  -Struts /a]
  +Once you have configured the Validator Plug-In, so that it can load your
  +Validator Resources you just have to extend
  +codeorg.apache.struts.validator.action.ValidatorForm/code instead of
  +codeorg.apache.struts.action.ActionForm/code.
  +Then when the codevalidate/code method is called, the action's name
  +attribute from the struts-config.xml is used to load the validations for
  +the current form.
  +So the form element's codename/code attribute in the
  +validator-rules.xml should match  action element's codename/code
  +attribute.
  +/p
  +
  +p
  +Another alternative is to use the action mapping you are currently on by
  +extending the ValidatorActionForm instead of the ValidatorForm.
  +The ValidatorActionForm uses the action element's codepath/code
  +attribute from the struts-config.xml which should match the form element's
  +codename/code attribute in the validator-rules.xml.
  +/p
  +
  +p
  +Then a separate action can be defined for each page in a multi-page form
  +and the validation rules can be associated with the action and not a page
  +number as in the example of a multi-page form in the validator example.
  +/p
  +
  +/section
  +
  +section href=i18n name=Internationalization
  +
  +p
  +Validation rules for forms can be grouped under a codeFormSet/code
  +element in the validator-rules.xml file.
  +The codeFormSet/code has language, country, and variant attributes that
  +correspond with the codejava.util.Locale/code class.
  +If they are not used, the codeFormSet/code  will be set to the default
  +locale.
  +A codeFormSet/code  can also have constants associated with it.
  +On the same level as a codeFormSet/code  there can be a global element
  +which can also have constants and have validator actions that perform
  +validations.
  +/p
  +
  +p
  +The default error message for a pluggable validator can be overriden with
  +the codemsg/code element.
  +So instead of using the codemsg/code attribute for the mask validator
  +to generate the error message the codemsg/code attribute from the
  +field will be used if the name of the field's name attribute matches the
  +validator's name attribute.
  +/p
  +
  +precode![CDATA[
  +field
  +property=lastName
  +depends=required,mask
  +msg
  +name=mask
  +key=registrationForm.lastname.maskmsg/
  +arg0 key=registrationForm.lastname.displayname/
  +var
  +var-namemask/var-name
  +var-value^[a-zA-Z]*$/var-value
  +/var
  +/field
  +]]/code/pre
  +
  +p
  +The arguments for error messages can be set with the arg0-arg3 elements.
  +If the arg0-arg3 elements' name attribute isn't set, it will become the
  +default arg value for the different error messages constructed.
  +If the name attribute is set, you can specify the argument for a specific
  +pluggable validator and then this will be used for constructing the error
  +message.
  +/p
  +
  +precode![CDATA[
  +field
  +property=lastName
  +depends=required,mask
  +msg
  +name=mask
  +key=registrationForm.lastname.maskmsg/
  +arg0 key=registrationForm.lastname.displayname/
  +var
  +var-namemask/var-name
  +var-value^[a-zA-Z]*$/var-value
  +/var
  +/field
  +]]/code/pre
  +
  +p
  +By default the arg0-arg3 elements will try to look up the codekey/code
  +attribute in the message resources.
  +If the resource attribute is set to false, it will pass in the value directly
  +without retrieving the value from the message resources.
  +/p
  +
  +precode![CDATA[
  +field
  +property=integer
  +depends=required,integer,range
  +arg0 key=typeForm.integer.displayname/
  +arg1
  +name=range
  +key=${var:min}
  +resource=false/
  +arg2
  +name=range
  +key=${var:max}
  +resource=false/
  +var
  +var-namemin/var-name
  

cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2002-12-07 Thread rleland
rleland 2002/12/07 14:41:34

  Modified:doc/userGuide dev_validator.xml
  Log:
  Remove warning about commons-validator LOCALE bug,
  replace it with a BugZilla query.
  
  Revision  ChangesPath
  1.15  +6 -7  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.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- dev_validator.xml 16 Nov 2002 05:06:48 -  1.14
  +++ dev_validator.xml 7 Dec 2002 22:41:34 -   1.15
  @@ -57,13 +57,12 @@
   /ul
   /section
   section href=validator-bugs name=Known Bugs
  -p The Struts Validator relies on the commons-validator. As of November 15 there
  -is a bug for non default LOCALE's that prevents validation from working.
  -Stated another way, if the browser and server locales do not match, validation will 
fail.
  -See 
  -a href=http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14384;Bugzilla bug 
14384 /a.
  -Until the commons validator is fixed, you must rebuild the validator with this 
patch applied.
  -/p
  +p Current know bugs can be found by clicking:
  +a 
href=http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMEDamp;bug_status=NEWamp;bug_status=ASSIGNEDamp;bug_status=REOPENEDamp;bug_status=VERIFIEDamp;bug_severity=Blockeramp;bug_severity=Criticalamp;bug_severity=Majoramp;bug_severity=Normalamp;bug_severity=Minoramp;email1=amp;emailtype1=substringamp;emailassigned_to1=1amp;email2=amp;emailtype2=substringamp;emailreporter2=1amp;bugidtype=includeamp;bug_id=amp;changedin=amp;votes=amp;chfieldfrom=amp;chfieldto=Nowamp;chfieldvalue=amp;product=Strutsamp;version=1.1+Beta+1amp;version=1.1+Beta+2amp;version=Nightly+Buildamp;version=Unknownamp;component=Validator+Frameworkamp;short_desc=amp;short_desc_type=allwordssubstramp;long_desc=amp;long_desc_type=allwordssubstramp;bug_file_loc=amp;bug_file_loc_type=allwordssubstramp;keywords=amp;keywords_type=anywordsamp;field0-0-0=noopamp;type0-0-0=noopamp;value0-0-0=amp;cmdtype=doitamp;newqueryname=amp;order=Reuse+same+sort+as+last+time;
  +Validation Bugs/a /p
  +pSince validation also relies on the commons-validator those bugs can be found
  +a 
href=http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMEDamp;bug_status=NEWamp;bug_status=ASSIGNEDamp;bug_status=REOPENEDamp;bug_status=VERIFIEDamp;bug_severity=Blockeramp;bug_severity=Criticalamp;bug_severity=Majoramp;bug_severity=Normalamp;bug_severity=Minoramp;email1=amp;emailtype1=substringamp;emailassigned_to1=1amp;email2=amp;emailtype2=substringamp;emailreporter2=1amp;bugidtype=includeamp;bug_id=amp;changedin=amp;votes=amp;chfieldfrom=amp;chfieldto=Nowamp;chfieldvalue=amp;product=Commonsamp;version=amp;component=Validatoramp;short_desc=amp;short_desc_type=allwordssubstramp;long_desc=amp;long_desc_type=allwordssubstramp;bug_file_loc=amp;bug_file_loc_type=allwordssubstramp;keywords=amp;keywords_type=anywordsamp;field0-0-0=noopamp;type0-0-0=noopamp;value0-0-0=amp;cmdtype=doitamp;newqueryname=amp;order=Reuse+same+sort+as+last+time;
  +here/a/p
   /section
   section href=validator-changes name=Changes and deprecations
   
  
  
  

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2002-11-15 Thread rleland
rleland 2002/11/15 21:06:48

  Modified:doc/userGuide dev_validator.xml
  Log:
  Document know bug in commons-validator that breaks code
  trying to validate non-default LOCALE's.
  
  Revision  ChangesPath
  1.14  +9 -0  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.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- dev_validator.xml 14 Nov 2002 19:25:15 -  1.13
  +++ dev_validator.xml 16 Nov 2002 05:06:48 -  1.14
  @@ -56,6 +56,15 @@
   /li
   /ul
   /section
  +section href=validator-bugs name=Known Bugs
  +p The Struts Validator relies on the commons-validator. As of November 15 there
  +is a bug for non default LOCALE's that prevents validation from working.
  +Stated another way, if the browser and server locales do not match, validation will 
fail.
  +See 
  +a href=http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14384;Bugzilla bug 
14384 /a.
  +Until the commons validator is fixed, you must rebuild the validator with this 
patch applied.
  +/p
  +/section
   section href=validator-changes name=Changes and deprecations
   
   p strongValidating against the DTD in the commons-validator.jar. /strong/p
  
  
  

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2002-11-11 Thread husted
husted  2002/11/11 13:33:04

  Modified:doc/userGuide dev_validator.xml
  Log:
  Add new resource.
  
  Revision  ChangesPath
  1.12  +7 -1  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.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- dev_validator.xml 4 Nov 2002 03:19:58 -   1.11
  +++ dev_validator.xml 11 Nov 2002 21:33:04 -  1.12
   -194,12 +194,18 
   
   section href=resources name=Validator Resources
   p
  +a href=http://www.strutskickstart.com/;
  +bDynaForms and the Validator/b/a by by James Turner and Kevin Bedell.
  +Sample chapter from 
  +a href=http://www.strutskickstart.com/;Struts Kickstart/a; 
  +available as a free download (PDF).
  +/p
  +p
   a 
href=http://www.manning.com/getpage.html?project=hustedamp;filename=chapters.html;
   bValidating user input/b/a by David Winterfeldt and Ted Husted.
   Sample chapter from 
   a 
href=http://www.amazon.com/exec/obidos/ISBN=1930110502/hitchhikeguidetoA/;Struts in 
Action/a; 
   available as a free download (PDF).
   /p
  -
   /section
   /chapter/body/document
  
  
  

--
To unsubscribe, e-mail:   mailto:struts-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:struts-dev-help;jakarta.apache.org




cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2002-11-03 Thread dgraham
dgraham 2002/11/03 19:19:58

  Modified:doc/userGuide dev_validator.xml
  Log:
  fixed typos
  
  Revision  ChangesPath
  1.11  +2 -2  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.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- dev_validator.xml 25 Oct 2002 22:10:42 -  1.10
  +++ dev_validator.xml 4 Nov 2002 03:19:58 -   1.11
   -41,7 +41,7 
 The validator xml files now validate against the DTD stored in the 
commons-validator.jar. 
   /li
   li
  -  The default valiator-rules.xml now ignores blank fields for all the basic 
validation types.
  +  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.
   /li
   -52,7 +52,7 
 Deprecation of range() methods in both JavaScript and Java
   /li
   li
  -  Deprecation of StrutsVlaidator amp; StrutsValidatorUtil
  +  Deprecation of StrutsValidator amp; StrutsValidatorUtil
   /li
   /ul
   
  
  
  

--
To unsubscribe, e-mail:   mailto:struts-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:struts-dev-help;jakarta.apache.org




cvs commit: jakarta-struts/doc/userGuide dev_validator.xml dev_tiles.xml

2002-10-25 Thread husted
husted  2002/10/25 05:37:53

  Modified:doc/userGuide dev_validator.xml dev_tiles.xml
  Log:
  + Add  book excerpts to Resource sections.
  
  Revision  ChangesPath
  1.9   +57 -28jakarta-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.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- dev_validator.xml 24 Oct 2002 18:42:20 -  1.8
  +++ dev_validator.xml 25 Oct 2002 12:37:53 -  1.9
   -11,39 +11,66 
   
   section href=validator name=Struts Validator
   
  +p
   [:TODO:]
  -pCover basic functionality as documented on David's web site.
  +/p
  +
  +p
  +Cover basic functionality as documented on David's web site.
   a href=http://home.earthlink.net/~dwinterfeldt/;Validation Framework for Struts 
/a 
   /p
   
  -p Struts 1.1 has added additional functionality over the original validator
  -contributed by David Winterfeldt/p
  +p
  +Struts 1.1 has added additional functionality over the original validator
  +contributed by David Winterfeldt.
  +/p
  +
   ul
  -li Conditionally required fields/li
  -li intRange() amp; floatRange() methods in both JavaScript and Java/li
  +li
  +  Conditionally required fields
  +/li
  +li
  +  intRange() amp; floatRange() methods in both JavaScript and Java
  +/li
   /ul
  -p There have also been changes in the validator behavior and deprecation of 
functionality
  +p
  +There have also been changes in the validator behavior and deprecation of 
functionality
   /p
   ul
  -li The validator xml files now validate against the DTD stored in the 
commons-validator.jar. /li
  -li The default valiator-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./li
  -li The Javascript Tag has new attributes defined. /li
  -li Deprecation of range() methods in both JavaScript and Java/li
  -li Deprecation of StrutsVlaidator amp; StrutsValidatorUtil/li
  +li
  +  The validator xml files now validate against the DTD stored in the 
commons-validator.jar. 
  +/li
  +li
  +  The default valiator-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.
  +/li
  +li
  +  The Javascript Tag has new attributes defined.
  +/li
  +li
  +  Deprecation of range() methods in both JavaScript and Java
  +/li
  +li
  +  Deprecation of StrutsVlaidator amp; StrutsValidatorUtil
  +/li
   /ul
   
   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 non-
  -null and field Y equals male./p
  +null and field Y equals male.
  +/p
  +
   p
   The syntax looks like this:
   /p
  +
   p
  -If you have this in your struts-config.xml /p
  +If you have this in your struts-config.xml
  +/p
  +
   ol
   pre![CDATA[
   form-bean name=dependentlistForm
   -57,11 +84,15 
   /form-bean
   ]]/pre
   /ol
  +
   p
   Where dependent is a bean that has properties lastName, firstName, dob, 
  -coverageType /p
  +coverageType
  +/p
  +
   p
  -You can define a validation:/p
  +You can define a validation:
  +/p
   
   pre![CDATA[
 form name=dependentlistForm
   -140,18 +171,16 
   indexed field as firstName.  Same thing for dob, except that we validate for 
   date if not blank.
   /p
  +
   p
   The coverageType is only required if the lastName for the same indexed bean is 
   not null, and also if the non-indexed field insureDependents is true.
   /p
  +
   p
   You can have an arbitrary number of fields by using the [n] syntax, the only 
   restriction is that they must all be AND or OR, you can't mix.
   /p
  -
  -
  -
  -
   /section
   
   section href=tiles name=Validator API Guide
   -163,14 +192,14 
   
   /section
   
  -!-- 
  -  authorTed Husted/author 
   section href=resources name=Validator Resources
  -pbuValidating Input/u/b by David Winterfeldt and Ted Husted. 
  -Sample chapter from uJava Web Development with Struts/u; available as a 
  -ufree download/u (PDF).
  +p
  +a 
href=http://www.manning.com/getpage.html?project=hustedamp;filename=chapters.html;
  +bValidating user input/b/a by Daid Winterfeldt and Ted Husted.
  +Sample chapter from 
  +a 
href=http://www.amazon.com/exec/obidos/ISBN=1930110502/hitchhikeguidetoA/;Struts in 
Action/a; 
  +available as a free download (PDF).
   /p
  -/section
  ---
   
  +/section
   /chapter/body/document
  
  
  
  1.10  +256 -256  jakarta-struts/doc/userGuide/dev_tiles.xml
  
  Index: dev_tiles.xml
  ===
  RCS 

cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2002-10-25 Thread rleland
rleland 2002/10/25 15:10:43

  Modified:doc/userGuide dev_validator.xml
  Log:
  Put the V back into
  David Winterfeldt name!
  
  Revision  ChangesPath
  1.10  +1 -1  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.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- dev_validator.xml 25 Oct 2002 12:37:53 -  1.9
  +++ dev_validator.xml 25 Oct 2002 22:10:42 -  1.10
   -195,7 +195,7 
   section href=resources name=Validator Resources
   p
   a 
href=http://www.manning.com/getpage.html?project=hustedamp;filename=chapters.html;
  -bValidating user input/b/a by Daid Winterfeldt and Ted Husted.
  +bValidating user input/b/a by David Winterfeldt and Ted Husted.
   Sample chapter from 
   a 
href=http://www.amazon.com/exec/obidos/ISBN=1930110502/hitchhikeguidetoA/;Struts in 
Action/a; 
   available as a free download (PDF).
  
  
  

--
To unsubscribe, e-mail:   mailto:struts-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:struts-dev-help;jakarta.apache.org




RE: cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2002-10-25 Thread James Mitchell
Speaking of David, I haven't heard from him in a while.  What gives?

James Mitchell
Software Engineer/Struts Evangelist
http://www.open-tools.org

Only two things are infinite, the universe and human stupidity, and I'm not
sure about the former.
- Albert Einstein (1879-1955)


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:rleland;apache.org]
 Sent: Friday, October 25, 2002 6:11 PM
 To: [EMAIL PROTECTED]
 Subject: cvs commit: jakarta-struts/doc/userGuide dev_validator.xml


 rleland 2002/10/25 15:10:43

   Modified:doc/userGuide dev_validator.xml
   Log:
   Put the V back into
   David Winterfeldt name!

   Revision  ChangesPath
   1.10  +1 -1  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.9
   retrieving revision 1.10
   diff -u -r1.9 -r1.10
   --- dev_validator.xml   25 Oct 2002 12:37:53 -  1.9
   +++ dev_validator.xml   25 Oct 2002 22:10:42 -  1.10
   @@ -195,7 +195,7 @@
section href=resources name=Validator Resources
p
a
 href=http://www.manning.com/getpage.html?project=hustedamp;filen
 ame=chapters.html
   -bValidating user input/b/a by Daid Winterfeldt and Ted Husted.
   +bValidating user input/b/a by David Winterfeldt and Ted Husted.
Sample chapter from
a
 href=http://www.amazon.com/exec/obidos/ISBN=1930110502/hitchhikeg
 uidetoA/Struts in Action/a;
available as a free download (PDF).




 --
 To unsubscribe, e-mail:
mailto:struts-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:struts-dev-help;jakarta.apache.org



--
To unsubscribe, e-mail:   mailto:struts-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:struts-dev-help;jakarta.apache.org




RE: cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2002-10-25 Thread Martin Cooper


 -Original Message-
 From: James Mitchell [mailto:jmitchtx;telocity.com]
 Sent: Friday, October 25, 2002 3:29 PM
 To: Struts Developers List
 Subject: RE: cvs commit: jakarta-struts/doc/userGuide 
 dev_validator.xml
 
 
 Speaking of David, I haven't heard from him in a while.  What gives?

I don't know what happened to David W - we haven't heard from him in a while
(on the list, at least). James Turner, on the other hand, is going great
guns to get Commons Validator fixed up and released. We're almost there.

--
Martin Cooper


 
 James Mitchell
 Software Engineer/Struts Evangelist
 http://www.open-tools.org
 
 Only two things are infinite, the universe and human 
 stupidity, and I'm not
 sure about the former.
 - Albert Einstein (1879-1955)
 
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:rleland;apache.org]
  Sent: Friday, October 25, 2002 6:11 PM
  To: [EMAIL PROTECTED]
  Subject: cvs commit: jakarta-struts/doc/userGuide dev_validator.xml
 
 
  rleland 2002/10/25 15:10:43
 
Modified:doc/userGuide dev_validator.xml
Log:
Put the V back into
David Winterfeldt name!
 
Revision  ChangesPath
1.10  +1 -1  
 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.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- dev_validator.xml 25 Oct 2002 12:37:53 -  1.9
+++ dev_validator.xml 25 Oct 2002 22:10:42 -  1.10
@@ -195,7 +195,7 @@
 section href=resources name=Validator Resources
 p
 a
  href=http://www.manning.com/getpage.html?project=hustedamp;filen
  ame=chapters.html
-bValidating user input/b/a by Daid Winterfeldt and 
 Ted Husted.
+bValidating user input/b/a by David Winterfeldt 
 and Ted Husted.
 Sample chapter from
 a
  href=http://www.amazon.com/exec/obidos/ISBN=1930110502/hitchhikeg
  uidetoA/Struts in Action/a;
 available as a free download (PDF).
 
 
 
 
  --
  To unsubscribe, e-mail:
 mailto:struts-dev-unsubscribe;jakarta.apache.org
 For additional commands, e-mail: 
mailto:struts-dev-help;jakarta.apache.org



--
To unsubscribe, e-mail:   mailto:struts-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:struts-dev-help;jakarta.apache.org



--
To unsubscribe, e-mail:   mailto:struts-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:struts-dev-help;jakarta.apache.org




Re: cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2002-10-25 Thread Rob Leland
James Mitchell wrote:


Speaking of David, I haven't heard from him in a while.  What gives?


Don't Know, last Email he sent to the list was in July,
Sometimes life gets in the way. :-/ I emailed him today to ask if
he wanted to donate the documentation from his web site to struts
directly. We'll see.

-Rob


--
To unsubscribe, e-mail:   mailto:struts-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:struts-dev-help;jakarta.apache.org




cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2002-10-24 Thread rleland
rleland 2002/10/24 11:42:20

  Modified:doc/userGuide dev_validator.xml
  Log:
  Updates changes to the validator behavior.
  
  Revision  ChangesPath
  1.8   +11 -5 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.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- dev_validator.xml 19 Oct 2002 21:44:53 -  1.7
  +++ dev_validator.xml 24 Oct 2002 18:42:20 -  1.8
   -21,11 +21,17 
   ul
   li Conditionally required fields/li
   li intRange() amp; floatRange() methods in both JavaScript and Java/li
  -li Do strongnot/strong use the lt;script/gt; to include static java script
  -as in the old validator example.
  - /li
  -li deprecation of range() methods in both JavaScript and Java/li
  -li deprecation of StrutsVlaidator amp; StrutsValidatorUtil/li
  +/ul
  +p There have also been changes in the validator behavior and deprecation of 
functionality
  +/p
  +ul
  +li The validator xml files now validate against the DTD stored in the 
commons-validator.jar. /li
  +li The default valiator-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./li
  +li The Javascript Tag has new attributes defined. /li
  +li Deprecation of range() methods in both JavaScript and Java/li
  +li Deprecation of StrutsVlaidator amp; StrutsValidatorUtil/li
   /ul
   
   p
  
  
  

--
To unsubscribe, e-mail:   mailto:struts-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:struts-dev-help;jakarta.apache.org




cvs commit: jakarta-struts/doc/userGuide dev_validator.xml

2002-10-19 Thread jholmes
jholmes 2002/10/19 14:44:53

  Modified:doc/userGuide dev_validator.xml
  Log:
  Cleaned up config file examples.  Thanks for the patch.
  
  PR: Bugzilla #13777
  
  Revision  ChangesPath
  1.7   +80 -48jakarta-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.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- dev_validator.xml 18 Oct 2002 16:58:09 -  1.6
  +++ dev_validator.xml 19 Oct 2002 21:44:53 -  1.7
   -39,14 +39,17 
   p
   If you have this in your struts-config.xml /p
   ol
  -prelt;form-bean name=dependentlistForm /pre
  -pre   type=org.apache.struts.webapp.validator.forms.ValidatorFormgt; 
/pre
  -pre   lt;form-property name=dependents /pre
  -pre   type=org.apache.struts.webapp.validator.Dependent[]/pre
  -pre   initial={'','','','','','','','','','',''}/gt;/pre
  -pre   lt;form-property name=insureDependents type=java.lang.Boolean 
/pre
  -pre   initial=false/gt;/pre
  -prelt;/form-beangt;/pre
  +pre![CDATA[
  +form-bean name=dependentlistForm
  +   type=org.apache.struts.webapp.validator.forms.ValidatorForm
  +form-property name=dependents 
  +   type=org.apache.struts.webapp.validator.Dependent[]
  +   initial={'','','','','','','','','','',''}/
  +form-property name=insureDependents
  +   type=java.lang.Boolean 
  +   initial=false/
  +/form-bean
  +]]/pre
   /ol
   p
   Where dependent is a bean that has properties lastName, firstName, dob, 
   -54,47 +57,76 
   p
   You can define a validation:/p
   
  -pre  lt;form name=dependentlistFormgt;/pre
  -prelt;field property=firstName indexedListProperty=dependents /pre
  -pre   depends=requiredifgt;/pre
  -pre  lt;arg0 key=dependentlistForm.firstName.label/gt;/pre
  -pre   lt;vargt;  lt;var-namegt;field[0]lt;/var-namegt;/pre
  -pre  lt;var-valuegt;lastNamelt;/var-valuegt;  lt;/vargt;/pre
  -pre   lt;vargt;  lt;var-namegt;field-indexed[0]lt;/var-namegt;/pre
 
  -pre  lt;var-valuegt;truelt;/var-valuegt;
lt;/vargt;/pre
  -pre   lt;vargt;  lt;var-namegt;field-test[0]lt;/var-namegt;/pre   
  
  -pre  lt;var-valuegt;NOTNULLlt;/var-valuegt; lt;/vargt;/pre
  -pre lt;/fieldgt;/pre
  -prelt;field property=dob indexedListProperty=dependents /pre
  -pre   depends=requiredif,dategt;/pre
  -pre  lt;arg0 key=dependentlistForm.dob.label/gt;/pre
  -pre  lt;vargt;   lt;var-namegt;field[0]lt;/var-namegt; /pre
  -pre  lt;var-valuegt;lastNamelt;/var-valuegt;  lt;/vargt;/pre
  -pre   lt;vargt;  lt;var-namegt;field-indexed[0]lt;/var-namegt;  /pre  
  
  -pre  lt;var-valuegt;truelt;/var-valuegt;
lt;/vargt;/pre
  -pre  lt;vargt;   lt;var-namegt;field-test[0]lt;/var-namegt;   /pre
   
  -pre  lt;var-valuegt;NOTNULLlt;/var-valuegt;lt;/vargt;/pre
  -pre lt;/fieldgt;/pre
  +pre![CDATA[
  +  form name=dependentlistForm
  +field property=firstName indexedListProperty=dependents
  +   depends=requiredif
  +  arg0 key=dependentlistForm.firstName.label/
  +  var
  +var-namefield[0]/var-name
  +var-valuelastName/var-value
  +  /var
  +  var
  +var-namefield-indexed[0]/var-name
  +var-valuetrue/var-value
  +  /var
  +  var
  +var-namefield-test[0]/var-name
  +var-valueNOTNULL/var-value
  +  /var
  +/field
  +field property=dob indexedListProperty=dependents 
  +   depends=requiredif,date
  +  arg0 key=dependentlistForm.dob.label/
  +  var
  +var-namefield[0]/var-name
  +var-valuelastName/var-value
  +  /var
  +  var
  +var-namefield-indexed[0]/var-name 
  +var-valuetrue/var-value
  +  /var
  +  var
  +var-namefield-test[0]/var-name
  +var-valueNOTNULL/var-value
  +  /var
  +/field
  +
  +field property=coverageType indexedListProperty=dependents
  +   depends=requiredif
  +  arg0 key=dependentlistForm.coverageType.label/
  +  var
  +var-namefield[0]/var-name  
  +var-valuelastName/var-value
  +  /var
  +  var
  +var-namefield-indexed[0]/var-name
  +var-valuetrue/var-value
  +  /var
  +  var
  +var-namefield-test[0]/var-name
  +var-valueNOTNULL/var-value
  +  /var
  +  var
  +var-namefield[1]/var-name  
  +var-valueinsureDependents/var-value
  +  /var
  +  var
  +var-namefield-test[1]/var-name
  +var-valueEQUAL/var-value
  +  /var
  +  var
  +var-namefield-value[1]/var-name
  +