You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2014/04/18 01:11:15 UTC
[jira] [Closed] (TAP5-2066) "tagName" property name in a form that
renders a zone leads to an "Forms require that the request method be POST
and that the t:formdata query parameter have values." error
[ https://issues.apache.org/jira/browse/TAP5-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-2066.
--------------------------------------
Resolution: Cannot Reproduce
I don't doubt this is an issue in Tapestry 5.3, but I just attempted to reproduce it in 5.4 and was unable to (which makes sense considering how different the client sides are). I don't think there is sufficient interest in back-porting a fix to 5.3, given that there's a simple workaround (once you find the problem).
> "tagName" property name in a form that renders a zone leads to an "Forms require that the request method be POST and that the t:formdata query parameter have values." error
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-2066
> URL: https://issues.apache.org/jira/browse/TAP5-2066
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.3.6
> Reporter: René Bernhardsgrütter
> Assignee: Howard M. Lewis Ship
>
> When I name a property "tagName" that's used in a form which submission leads to a zone update, I get the following error: "Forms require that the request method be POST and that the t:formdata query parameter have values.".
> After I renamed the "tagName" property to "userTagName", it worked correctly.
> Example:
> Java:
> @Property
> private String tagName;
> @Component
> private Zone tagZone;
> TML:
> <t:zone t:id="userTagZone" id="userTagZone">
> <!-- updated content -->
> <t:form t:id="addForm" t:zone="userTagZone">
> <t:textfield t:id="tagName" t:mixins="autocomplete"/>
> </t:form>
> </t:zone>
> It doesn't matter whether the form is in or out of the zone. I've tested the same also with this jumpstart page (http://jumpstart.doublenegative.com.au/jumpstart/examples/ajax/formmultiplezoneupdate) and a fresh Tapestry installation.
> This problem could be related to this:
> https://mail-archives.apache.org/mod_mbox/tapestry-users/201209.mbox/%3C504A3CC9.1000202@cerder.com%3E (I cannot reproduce this with the form/zone constellation here, but it goes in a similar manner.)
> http://tapestry.1045711.n5.nabble.com/t5-3-1-Heads-up-for-special-form-field-names-similar-to-InternalSymbols-PRE-SELECTED-FORM-NAMES-td5101482.html
> The big problem is not the bug itself, but that it's very hard to find. I've spent almost one and a half days to find it.
> A simple warning or error message, that would be displayed when such critical property names are in use, would do it.
--
This message was sent by Atlassian JIRA
(v6.2#6252)