tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lutz Hühnken (JIRA) <j...@apache.org>
Subject [jira] [Commented] (TAP5-1285) Allow GET method in form component
Date Sat, 31 May 2014 08:16:03 GMT

    [ https://issues.apache.org/jira/browse/TAP5-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14014568#comment-14014568
] 

Lutz Hühnken commented on TAP5-1285:
------------------------------------

Given HLS above comment I thought it was a "won't fix", which might be reasonable in this
case. I must admit I don't follow Tapestry development anymore, it's Scala & Play for
me now. But I think as far a affected versions go, it is still current. Will update accordingly.


> 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
>            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)

Mime
View raw message