[
https://issues.apache.org/jira/browse/TAP5-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675022#action_12675022
]
Joey Solis commented on TAP5-43:
--------------------------------
I don't think that using the "tapestry.production-mode" setting is the best
solution. I may still want to deploy unsecured pages in production mode.
Then, I'd have to remove all the @Secure annotations. I have to anticipate
these type of quick changes where I work. Ideally, I think there should be a
separate setting to toggle for secured/un-secured pages and components.
> 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.
