tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tony Deigh (JIRA)" <j...@apache.org>
Subject [jira] Created: (TAP5-856) MetaDataLocatorImpl.findMeta(String, String, Class) doesn't check contributed defaults - breaks SECURE_PAGE contributions
Date Fri, 25 Sep 2009 18:06:16 GMT
MetaDataLocatorImpl.findMeta(String, String, Class) doesn't check contributed defaults - breaks
SECURE_PAGE contributions
-------------------------------------------------------------------------------------------------------------------------

                 Key: TAP5-856
                 URL: https://issues.apache.org/jira/browse/TAP5-856
             Project: Tapestry 5
          Issue Type: Bug
          Components: tapestry-core
    Affects Versions: 5.1.0.5
            Reporter: Tony Deigh
            Priority: Minor


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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message