Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-1290

Add required flag to @ActivationRequestParameter annotation

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.2
    • Fix Version/s: 5.4
    • Component/s: None
    • Labels:
      None
    • Environment:
      Tapestry 5.2.0 alpha

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              hlship Howard M. Lewis Ship
              Reporter:
              vjeran@tis.hr Vjeran Marcinko
            • Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: