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

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.1.0.5
• Fix Version/s: 5.2.0
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Tony Deigh
• Created: 25/Sep/09 18:04
• Updated: 13/Jan/10 00:54
• Resolved: 13/Jan/10 00:54

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.