[jira] Updated: (TAP5-156) Add an @QueryParameter annotation for parameter to event handler method

["Howard M. Lewis Ship (JIRA)" <ji...@apache.org>]

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

Howard M. Lewis Ship updated TAP5-156:
--------------------------------------

    Description: 
It would be nice, is some cases, to have Tapestry map query parameters to event handler method parameters, rather than path info.  This is typically about the Ajax case, where it is more reliable (and easier) to take a URL and add query parameters to it than it is to add extra path info.

public void onActionFromAjaxWidget(@QueryParameter("action") String widgetAction, @QueryParameter("count") int count) { .... }


  was:
It would be nice, is some cases, to have Tapestry map query parameters to event handler method parameters, rather than path info.  This is typically about the Ajax case, where it is more reliable (and easier) to take a URL and add query parameters to it than it is to add extra path info.

public void onActionFromAjaxWidget(@QueryParameter("action") String widgetAction, @QueryParameter("count") int count) { .... }

This does raise some tricky questions: i.e., what do you do when only some of the parameters have @QueryParameter?

        Summary: Add an @QueryParameter annotation for parameter to event handler method  (was: Annotation to map query parameter to event handler method)

> Add an @QueryParameter annotation for parameter to event handler method
> -----------------------------------------------------------------------
>
>                 Key: TAP5-156
>                 URL: https://issues.apache.org/jira/browse/TAP5-156
>             Project: Tapestry 5
>          Issue Type: New Feature
>    Affects Versions: 5.0.15
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>
> It would be nice, is some cases, to have Tapestry map query parameters to event handler method parameters, rather than path info.  This is typically about the Ajax case, where it is more reliable (and easier) to take a URL and add query parameters to it than it is to add extra path info.
> public void onActionFromAjaxWidget(@QueryParameter("action") String widgetAction, @QueryParameter("count") int count) { .... }

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.