[prev in list] [next in list] [prev in thread] [next in thread] 

List:       tapestry-dev
Subject:    [jira] [Resolved] (TAP5-1285) Allow GET method in form component
From:       "Thiago H. de Paula Figueiredo (JIRA)" <jira () apache ! org>
Date:       2014-05-31 13:22:01
Message-ID: JIRA.12475325.1285696546792.53413.1401542521977 () arcas
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/TAP5-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Thiago H. de Paula Figueiredo resolved TAP5-1285.
-------------------------------------------------

    Resolution: Won't Fix

> Allow GET method in form component
> ----------------------------------
> 
> Key: TAP5-1285
> URL: https://issues.apache.org/jira/browse/TAP5-1285
> Project: Tapestry 5
> Issue Type: Wish
> Components: tapestry-core
> Affects Versions: 5.3.7, 5.4
> Reporter: Lutz Hühnken
> Priority: Minor
> 
> The Tapestry form component is currently only supporting the "POST" method.
> The POST method is usually associated with changing the "model" on the server side, \
> e.g. in REST applications, POST indicates that a resource is modified, if I am not \
> mistaken. The lack of GET support makes it necessary to use POST also for simple \
> queries, such as a search field, where the model is not modified. This is a) \
> semantically irritating, since for example a search query will not modify state and \
> b) requires extra "work", for example a redirect-after-post, where it should not be \
> necessary. Since Tapestry aspires to make the simple things easy, the difficult \
> things possible, I think it should provide first-class support for the GET method.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[prev in list] [next in list] [prev in thread] [next in thread]