[
https://issues.apache.org/jira/browse/TAP5-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ulrich Stärk updated TAP5-1290:
-------------------------------
Affects Version/s: 5.2.0
> 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.0
> Environment: Tapestry 5.2.0 alpha
> Reporter: Vjeran Marcinko
>
> 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 is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
