Return-Path: 
 <commits-return-13363-apmail-tapestry-commits-archive=tapestry.apache.org@tapestry.apache.org>
X-Original-To: apmail-tapestry-commits-archive@minotaur.apache.org
Delivered-To: apmail-tapestry-commits-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 4A9CA7D59
	for <apmail-tapestry-commits-archive@minotaur.apache.org>;
 Tue,  9 Aug 2011 18:49:53 +0000 (UTC)
Received: (qmail 51858 invoked by uid 500); 9 Aug 2011 18:49:53 -0000
Delivered-To: apmail-tapestry-commits-archive@tapestry.apache.org
Received: (qmail 51678 invoked by uid 500); 9 Aug 2011 18:49:52 -0000
Mailing-List: contact commits-help@tapestry.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@tapestry.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@tapestry.apache.org>
List-Post: <mailto:commits@tapestry.apache.org>
List-Id: <commits.tapestry.apache.org>
Reply-To: dev@tapestry.apache.org
Delivered-To: mailing list commits@tapestry.apache.org
Received: (qmail 51573 invoked by uid 99); 9 Aug 2011 18:49:51 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Aug 2011 18:49:51 +0000
X-ASF-Spam-Status: No, hits=-2000.8 required=5.0
	tests=ALL_TRUSTED,RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Aug 2011 18:49:49 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 49B6CB4490
	for <commits@tapestry.apache.org>; Tue,  9 Aug 2011 18:49:28 +0000 (UTC)
Date: Tue, 9 Aug 2011 18:49:28 +0000 (UTC)
From: "Howard M. Lewis Ship (JIRA)" <jira@apache.org>
To: commits@tapestry.apache.org
Message-ID: 
 <1150560149.21169.1312915768298.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (TAP5-1285) Allow GET method in form component
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


    [ https://issues.apache.org/jira/browse/TAP5-1285?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13081=
837#comment-13081837 ]=20

Howard M. Lewis Ship commented on TAP5-1285:
--------------------------------------------

It's quite reasonable to build a form without the Form component.

<form method=3D"get" action=3D"${pageActivationURL}"> ... <input type=3D"te=
xt" name=3D"q" ....

Then in your Java code you provide the pageActivationURL, and an activate e=
vent handler.  You can leverage the PageRenderLinkSource service to generat=
e the URL, and the @RequestParameter  or @ActivationRequestParameter annota=
tions 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=C3=BChnken
>            Priority: Minor
>
> The Tapestry form component is currently only supporting the "POST" metho=
d.
> The POST method is usually associated with changing the "model" on the se=
rver side, e.g. in REST applications, POST indicates that a resource is mod=
ified, if I am not mistaken.
> The lack of GET support makes it necessary to use POST also for simple qu=
eries, 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 sho=
uld not be necessary.
> Since Tapestry aspires to make the simple things easy, the difficult thin=
gs possible, I think it should provide first-class support for the GET meth=
od.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira