[TAP5-2138] Support multiple @PageActivationContext

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 5.4
• Assignee: Lance S
• Reporter: Lance S
• Created: 01/Jul/13 11:58
• Updated: 26/Jun/14 20:53
• Resolved: 26/Jun/14 20:15

Description

The @PageActivationContext annotation (and PageActivationContextWorker) could be improved to accept an "index" parameter. This way, I could have multiple @PageActivationContext properties.

eg

public class MyPage {
   @PageActivationContext(index=0)
   private Category category;

   @PageActivationContext(index=1)
   private Item item;

   ...
}

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