tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan Dubrov (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TAP5-264) Lack of direct support for named context parameters
Date Mon, 13 Oct 2008 10:16:44 GMT

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

Ivan Dubrov commented on TAP5-264:

I vote for something similar to activation parameters, but with names. So you have field @QueryParameter
int page; and it is added to URL as ?page=<value>. Also, createPageLink/createEventLink/etc
should have possibility to override named parameters as well as regular page context parameters
(by providing map of overrides or something like this).

The idea is illustrated here: http://www.nabble.com/Re%3A-%22named%22-page-context-parameters---p19893835.html

> Lack of direct support for named context parameters
> ---------------------------------------------------
>                 Key: TAP5-264
>                 URL: https://issues.apache.org/jira/browse/TAP5-264
>             Project: Tapestry 5
>          Issue Type: Improvement
>    Affects Versions: 5.0.16
>            Reporter: Francois Armand
> T5 "REST" orientation make easy the mappin between url and resources, but it lack the
possibility to add "normal" named parameters.
> This one are quite handy when one's want to make big queries bookmarkable. For example,
in a application that send email to dynamic mailing list build as the result of a search in
the company user base, it would be great if each user can bookmark his most used filter/dynamic
> The implementation can fit quite well with the current T5 implementation if we add a
direct mapping of the kind :
> In URL map=[string=string,string=string] becomes a Map<String,String> in onActivate.
I think that we can limit the use of Map<String,String> (at least for 5.0).
> For example :
> http://foo/myT5app/mypage/normalcontext/mycontextmap=[key1:value1,key2:value2]/othercontextparam
> => in the Java code :
> void onActivate(String normalcontext, Map<String,String> mycontextmap, String othercontextparam)
>   String username = normalcontext:
>   String telephone = mycontextmap.get("key1"); //let the user handle the type
>   String email=mycontextmap.get("key2");
>   String eqalityType=othercontextparam;
>   ....
> }

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

To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

View raw message