[
https://issues.apache.org/jira/browse/TAPESTRY-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620475#action_12620475
]
Massimo Lusetti commented on TAPESTRY-2547:
-------------------------------------------
Well I've external devices (handheld / palm PCs) which are used to collect data
and perform operations then when are put back into the cradle there's a custom
application which download data from the devices and send it to a custom
tapestry page/component which process the data and simply return a status code.
I've to hardcode (sort of) the t:formdata parameter into the application to let
tapestry correctly handle the http post and this turned out to work as expected
but this put the upgrade of server side (T5 web application) and client side
(T5 IoC swing application) into a nightmare cause t:formadata parameter changes
so i cannot upgrade the server side without release and distribute and upgrade
to all clients.
So this could be a use case where having T5 process the form without t:formdata
parameter is a very big plus.
It's just me using the power of T5 this way?
This is all production code already in use since April.
> 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
>
> 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]
