[jira] [Created] (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

["René Bernhardsgrütter (JIRA)" <ji...@apache.org>]

René Bernhardsgrütter created TAP5-2066:
-------------------------------------------

             Summary: "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


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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira