You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tapestry.apache.org by "Lance (JIRA)" <ji...@apache.org> on 2014/06/26 22:17:24 UTC

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

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

Lance resolved TAP5-2138.
-------------------------

       Resolution: Fixed
    Fix Version/s: 5.4

> 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
>             Fix For: 5.4
>
>
> 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)