You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2010/01/13 01:08:55 UTC
[jira] Assigned: (TAP5-856) MetaDataLocatorImpl.findMeta(String,
String, Class) doesn't check contributed defaults - breaks SECURE_PAGE
contributions
[ https://issues.apache.org/jira/browse/TAP5-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-856:
-----------------------------------------
Assignee: Howard M. Lewis Ship
> 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
> Assignee: Howard M. Lewis Ship
> 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.