[
https://issues.apache.org/jira/browse/TAP5-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14045165#comment-14045165
]
Hudson commented on TAP5-2138:
------------------------------
FAILURE: Integrated in tapestry-trunk-freestyle #1254 (See
[https://builds.apache.org/job/tapestry-trunk-freestyle/1254/])
TAP5-2138: Support multiple @PageActivationContext (uklance: rev
b02c35148bb74eca48b96bb768982336815a9635)
* tapestry-core/src/test/app1/PACMultipleAnnotationDemo.tml
*
tapestry-core/src/test/java/org/apache/tapestry5/integration/app1/pages/PACMultipleAnnotationDemo.java
*
tapestry-core/src/test/java/org/apache/tapestry5/integration/app1/CoreBehaviorsTests.java
*
tapestry-core/src/test/java/org/apache/tapestry5/integration/app1/pages/Index.java
*
tapestry-core/src/main/java/org/apache/tapestry5/internal/transform/PageActivationContextWorker.java
*
tapestry-core/src/main/java/org/apache/tapestry5/annotations/PageActivationContext.java
> 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)
