Differences between revisions 1 and 2
Revision 1 as of 2004-05-20 20:36:20
Size: 1618
Editor: 82-38-65-173
Comment: Moved content from original wiki
Revision 2 as of 2004-05-20 20:37:39
Size: 1569
Editor: 82-38-65-173
Comment:
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
 * '''distributable config files''' - It would be nice if the validation.xml could be split up so that the validation.xml could be stored in jars and brought together in a central validation.xml config  * '''distributable config files''' - It would be nice if the validation.xml could be split up so that the validation.xml could be stored in jars and brought together in a central validation.xml config
Line 10: Line 10:
 * '''Extendable validation configs''' - It would also be cool if validation configs were extendable. Sometimes several beans have some commons requirements. This would be similar to TilesExtendableDefinitions.  * '''Extendable validation configs''' - It would also be cool if validation configs were extendable. Sometimes several beans have some commons requirements. This would be similar to TilesExtendableDefinitions.
Line 12: Line 12:
 * '''Continuous error-checking with indexed properties'''  - The validator stops checking for errors when it finds an error with indexed properties. It would be nice if the validator continued checking and caught ''all'' errors of the indexed property. Maybe even better: make this an optional feature!  * '''Continuous error-checking with indexed properties''' - The validator stops checking for errors when it finds an error with indexed properties. It would be nice if the validator continued checking and caught ''all'' errors of the indexed property. Maybe even better: make this an optional feature!
Line 14: Line 14:
 * '''Multiple-Fields-Validation''' - It would be more than cool to apply validation rules  * '''Multiple-Fields-Validation'''- It would be more than cool to apply validation rules
Line 17: Line 17:
 * '''Documented-Examples''' - To become more useful, some documented application examples  * '''Documented-Examples''' - To become more useful, some documented application examples
Line 20: Line 20:
 * '''RegExp field names''' If the property attribute of the <field> element allowed for regular expressions or even simply supported an asterisk for wild card matching.  * '''RegExp field names''' - If the property attribute of the <field> element allowed for regular expressions or even simply supported an asterisk for wild card matching.
Line 22: Line 22:
 * '''Handling of float, double and bigDecimal'''should honor the locale of the user. Converting from a string to a double using <code>new Double(s)</code> will breake outside of USA.  * '''Handling of float, double and bigDecimal''' should honor the locale of the user. Converting from a string to a double using <code>new Double(s)</code> will breake outside of USA.

Up to [:Validator]


Validator Wish List

A space for wishes validator future functionality.

  • distributable config files - It would be nice if the validation.xml could be split up so that the validation.xml could be stored in jars and brought together in a central validation.xml config

  • Extendable validation configs - It would also be cool if validation configs were extendable. Sometimes several beans have some commons requirements. This would be similar to TilesExtendableDefinitions.

  • Continuous error-checking with indexed properties - The validator stops checking for errors when it finds an error with indexed properties. It would be nice if the validator continued checking and caught all errors of the indexed property. Maybe even better: make this an optional feature!

  • Multiple-Fields-Validation- It would be more than cool to apply validation rules

to more than one field (if <field-a.fulfills_condition> and/or <field-b.fulfills_anothercondition>)

  • Documented-Examples - To become more useful, some documented application examples

apart from those printed in books could be supplied.

  • RegExp field names - If the property attribute of the <field> element allowed for regular expressions or even simply supported an asterisk for wild card matching.

  • Handling of float, double and bigDecimal should honor the locale of the user. Converting from a string to a double using <code>new Double(s)</code> will breake outside of USA.


Up to [:Validator]

ValidatorWishList (last edited 2009-09-20 23:48:54 by localhost)