[jira] [Commented] (TAP5-2138) Support multiple @PageActivationContext

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on TAP5-2138:
-------------------------------------------------------

Commit b02c35148bb74eca48b96bb768982336815a9635 in tapestry-5's branch refs/heads/master from [~uklance]
[ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=b02c351 ]

TAP5-2138: Support multiple @PageActivationContext


> Support multiple @PageActivationContext
> ---------------------------------------
>
>                 Key: TAP5-2138
>                 URL: https://issues.apache.org/jira/browse/TAP5-2138
>             Project: Tapestry 5
>          Issue Type: Improvement
>            Reporter: Lance
>            Assignee: Lance
>            Priority: Minor
>
> The @PageActivationContext annotation (and PageActivationContextWorker) could be improved to accept an "index" parameter. This way, I could have multiple @PageActivationContext properties.
> eg
> {code}
> public class MyPage {
>    @PageActivationContext(index=0)
>    private Category category;
>    @PageActivationContext(index=1)
>    private Item item;
>    ...
> }
> {code}
> I'd expect tapestry to generate the following URL's:
> - /mypage (category and item is null)
> - /mypage/category1 (item is null)
> - /mypage/$N/item1 (category is null)
> - /mypage/category1/item1 
>    



--
This message was sent by Atlassian JIRA
(v6.2#6252)