commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From commons-...@jakarta.apache.org
Subject [Jakarta Commons Wiki] Updated: ValidatorWishList
Date Thu, 20 May 2004 20:37:40 GMT
   Date: 2004-05-20T13:37:40
   Editor: RobertBurrellDonkin <rdonkin@apache.org>
   Wiki: Jakarta Commons Wiki
   Page: ValidatorWishList
   URL: http://wiki.apache.org/jakarta-commons/ValidatorWishList

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -5,21 +5,21 @@
 
 A space for wishes validator future functionality.
 
- * '''distributable config files'''&nbsp;-&nbsp;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
 
- * '''Extendable validation configs'''&nbsp;-&nbsp;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.
 
- * '''Continuous error-checking with indexed properties''' &nbsp;-&nbsp;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!
 
- * '''Multiple-Fields-Validation'''&nbsp;-&nbsp;It would be more than cool to apply
validation rules
+ * '''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'''&nbsp;-&nbsp;To become more useful, some documented application
examples
+ * '''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.
+ * '''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.
+ * '''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.
 
 ----
 

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message