Tapestry 5
  1. Tapestry 5
  2. TAP5-1651

It should be possible for a LinkCreationListener to override Tapestry and make a Link secure or insecure after the fact

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.3
    • Fix Version/s: 5.3
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      The use case here is a client who has created rules about which paths (not pages) should be secure.

      This will involve adding two new methods to the Link interface; however Link is not implemented in user code, so this should not cause a problem with backwards compatibility.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Howard M. Lewis Ship
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development