[
https://issues.apache.org/jira/browse/TAP5-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675032#action_12675032
]
Ulrich Stärk commented on TAP5-43:
----------------------------------
why not do something like
public static void contributeApplicationDefaults(MappedConfiguration<String,
String> configuration)
{
configuration.add("https", "true");
}
public void contributeMetaDataLocator(MappedConfiguration<String,String>
configuration, @Inject @Symbol("https") String https)
{
configuration.add("admin:" + MetaDataConstants.SECURE_PAGE, https);
}
In your AppModule and override this with -Dhttps=false on the command line
during development?
> Add configuration to turn off @Secure when in development
> ---------------------------------------------------------
>
> Key: TAP5-43
> URL: https://issues.apache.org/jira/browse/TAP5-43
> Project: Tapestry 5
> Issue Type: New Feature
> Affects Versions: 5.0.15
> Environment: Windows XP
> Reporter: Joey Solis
> Assignee: Kevin Menard
>
> In production I want my pages to be secured so I annotate my them with
> @Secure.
> In development however, I don't want my pages to have to be secured (https)
> so I comment out the @Secure annotation.
> It would be nice to be able to set the @Secure dynamically based on the
> environment (development or production).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
