Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
None
-
None
-
None
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