[jira] [Commented] (TAP5-1290) Add required flag to @ActivationRequestParameter annotation

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

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

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

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

TAP5-1290: Add required flag to @ActivationRequestParameter annotation


> Add required flag to @ActivationRequestParameter annotation
> -----------------------------------------------------------
>
>                 Key: TAP5-1290
>                 URL: https://issues.apache.org/jira/browse/TAP5-1290
>             Project: Tapestry 5
>          Issue Type: Improvement
>    Affects Versions: 5.2
>         Environment: Tapestry 5.2.0 alpha
>            Reporter: Vjeran Marcinko
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.4
>
>
> It would be really nice to have "required" argument in @ActivationRequestParameter so one doesn't have to check it manually before page rendering begins.
> I guess many people such as me, who don't care about RESTful URLs, will find @ActivationRequestParameter much easier way to pass render parameters than standard activation context, not just because it offers naming and optionality, but also because one have clean separation between parameter setting process (through this annotation) and preprocessing logic needed for some pages (placed in onActivate, such as security check or other mutli page preprocesing logic; request filters is sometimes too cumbersome way to achieve the same). Required flag would be nice addition to make it truly top-level way to pass render params.



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