[ 
https://issues.apache.org/jira/browse/TAPESTRY-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618968#action_12618968
 ] 

Francois Armand commented on TAPESTRY-2547:
-------------------------------------------

A trivial workaround exists : we just have to perform all validation on 
onValidateFromForm, but it's really painful. Moreover, data consistency is 
always a critical area, and T5 is close to a final version, so I choose blocker 
priority.


> Field validation is bypassed if form action url is used as a GET url
> --------------------------------------------------------------------
>
>                 Key: TAPESTRY-2547
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2547
>             Project: Tapestry
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.0.13
>            Reporter: Francois Armand
>            Priority: Blocker
>
> We have a form, the simpliest one is ok, say this one on "TestPage" page :
> <t:form>
>       <t:textfield t:id="field" t:validate="required" t:value="value" />
>       <t:submit/>
> </t:form>
> This form is supposed to required a a non empty value for value. 
> All goes fine if we click on ok, but if a twisted tester try to enter 
> directly the action url in the browser ( t5app/testpage.form), the field 
> level validation are bypassed (but all form events are throws and so the one 
> done in "onValidateFormFrom" arecorrectly performed).
> The result is that the form may be successful with inconsistent data, in our 
> case a null value. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Reply via email to