[
https://issues.apache.org/jira/browse/TAP5-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAP5-761.
-------------------------------------
Resolution: Duplicate
Assignee: Howard M. Lewis Ship
This is fixed as part of TAP5-856.
> Global meta data "secure-page" does not work anymore with 5.1
> -------------------------------------------------------------
>
> Key: TAP5-761
> URL: https://issues.apache.org/jira/browse/TAP5-761
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.1.0.0, 5.1.0.1, 5.1.0.2, 5.1.0.3, 5.1.0.4, 5.1.0.5, 5.1
> Reporter: Christian Köberl
> Assignee: Howard M. Lewis Ship
>
> Adding the following code to the app module (as documented in
> http://tapestry.apache.org/tapestry5.1/guide/secure.html) does not work
> anymore with Tapestry 5.1:
> public void contributeMetaDataLocator(MappedConfiguration<String,String>
> configuration)
> {
> configuration.add(MetaDataConstants.SECURE_PAGE, "true");
> }
> It seems that this is now replaced with symbols. See also
> http://n2.nabble.com/problem-with-%22Secure%22-configuration-td2457869.html
> Is this correct`?
> - if yes please fix documentation (and add it to 5.1 release notes!!)
> - if no please fix code
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
