tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] Moved: (TAP5-1290) Add required flag to @ActivationRequestParameter annotation
Date Fri, 01 Oct 2010 16:54:34 GMT

     [ https://issues.apache.org/jira/browse/TAP5-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Howard M. Lewis Ship moved TAPESTRY-2768 to TAP5-1290:

              Project: Tapestry 5  (was: Tapestry)
                  Key: TAP5-1290  (was: TAPESTRY-2768)
    Affects Version/s:     (was: unspecified)
           Issue Type: Bug  (was: Improvement)
          Component/s:     (was: tapestry-core)

> Add required flag to @ActivationRequestParameter annotation
> -----------------------------------------------------------
>                 Key: TAP5-1290
>                 URL: https://issues.apache.org/jira/browse/TAP5-1290
>             Project: Tapestry 5
>          Issue Type: Bug
>         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.
You can reply to this email to add a comment to the issue online.

View raw message