[
https://issues.apache.org/jira/browse/TAP5-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081837#comment-13081837
]
Howard M. Lewis Ship commented on TAP5-1285:
--------------------------------------------
It's quite reasonable to build a form without the Form component.
<form method="get" action="${pageActivationURL}"> ... <input type="text"
name="q" ....
Then in your Java code you provide the pageActivationURL, and an activate event
handler. You can leverage the PageRenderLinkSource service to generate the
URL, and the @RequestParameter or @ActivationRequestParameter annotations to
get the value of the field.
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
