You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by bu...@apache.org on 2003/08/30 19:20:59 UTC

DO NOT REPLY [Bug 22838] New: - Add client-size validation to NumericField and ValidatingTextField components

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22838>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22838

Add client-size validation to NumericField and ValidatingTextField components

           Summary: Add client-size validation to NumericField and
                    ValidatingTextField components
           Product: Tapestry
           Version: 3.0
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Contrib
        AssignedTo: tapestry-dev@jakarta.apache.org
        ReportedBy: juceri@ya.com


After fixing bug 22837:

Check using javascript that the number format is correct differentiating 
between integer format and float format.

I have added a clientScriptingEnabled parameter to these components and transfer
it in the getValidator method doing:
   public IValidator getValidator()
   {
   ...... 
      if (clientScriptingEnabledBinding != null)
      {
         boolean clientScriptingEnabled =
clientScriptingEnabledBinding.getBoolean();
         validator.setClientScriptingEnabled(clientScriptingEnabled);		
      }
   .....
   }
   
I have modified NumberValidator.java for add a "invalid integer format" message
and a method (boolean isRealNumber()) for check from the script if the number to
validate has a integer format or a float format.
I have added some code to NumberValidator.script.

I have done similar changes to the ValidatingTextField component.