tapestry-dev mailing list archives

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

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

Joel Halbert commented on TAP5-264:

 Regarding Massimo's comment : "Talking about the T5 "REST" orientation... how would you consider
the presence of T5 hidden formdata field within forms?"

My Comment: From an end users perspective it might would be ideal if named parameters (whether
from hidden fields, or url encoded) could be handled on the server side (i.e. retrieved and
accessed) in the same way - i.e. the difference between url encoded and hidden fields on the
server side was  mostly transparent.

> 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