You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Michal Prinke <bo...@icpnet.pl> on 2004/08/04 01:58:07 UTC

"required" set to "false" turns off client-side validation ?

Hello,

I've got this simple validator:

   <bean name="vldtr" class="org.apache.tapestry.valid.NumberValidator">
     <set-property name="clientScriptingEnabled" expression="true"/>
     <set-property name="required" expression="false"/>
   </bean>

The problem is that it does not check whether user entered a valid
number on the client-side. But when I set required to "true",
it starts to validate the numeric format on the client-side.

Is it a bug? Maybe it was corrected in some newer version of Tapestry
(I've got 3.0).

Thanks for any help!



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


Re: "required" set to "false" turns off client-side validation ?

Posted by Jamie Orchard-Hays <ja...@dang.com>.
There was a similar post a week or two ago about this. If you look in the
NumberValidator.script file, you'll see that the client side code hasn't
really been developed. The component is currently only useful using server
side validation.

Jamie
----- Original Message ----- 
From: "Michal Prinke" <bo...@icpnet.pl>
To: "Tapestry" <ta...@jakarta.apache.org>
Sent: Tuesday, August 03, 2004 7:58 PM
Subject: "required" set to "false" turns off client-side validation ?


> Hello,
>
> I've got this simple validator:
>
>    <bean name="vldtr" class="org.apache.tapestry.valid.NumberValidator">
>      <set-property name="clientScriptingEnabled" expression="true"/>
>      <set-property name="required" expression="false"/>
>    </bean>
>
> The problem is that it does not check whether user entered a valid
> number on the client-side. But when I set required to "true",
> it starts to validate the numeric format on the client-side.
>
> Is it a bug? Maybe it was corrected in some newer version of Tapestry
> (I've got 3.0).
>
> Thanks for any help!
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>


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