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

Joel Halbert commented on TAP5-264:
-----------------------------------

I would agree with Geoff & Ivan comments that using the activation context is 
probably not the right way forward and that use of annotations would be a more 
elegant solution. 
I would advocate that, although the default encoding used should of course be 
sensible (e.g. a=b?c=d etc...), the user should ultimately be able to define 
their own encoding scheme by overriding the default.

Also - any thoughts on modifying  the current @Persist("client") behaviour to 
achieve some of these goals?

> 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 ml.
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to