Tapestry 5
  1. Tapestry 5
  2. TAP5-856

MetaDataLocatorImpl.findMeta(String, String, Class) doesn't check contributed defaults - breaks SECURE_PAGE contributions

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 5.1.0.5
    • Fix Version/s: 5.2.0
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      The new overload of MetaDataLocator.findMeta, which takes a page name, does not check the configured defaults, as the other overload does. This breaks the documented means of adding SECURE_PAGE meta data to multiple pages (which is to contribute them to the MetaDataLocator configuration), since RequestSecurityManagerImpl.isSecure uses this new method.

        Activity

        There are no comments yet on this issue.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development