[
https://issues.apache.org/jira/browse/TRINIDAD-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anand V Nath updated TRINIDAD-2475:
-----------------------------------
Status: Patch Available (was: Open)
> org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION context parameter warning
> in non Production stage
> -----------------------------------------------------------------------------------------------------
>
> Key: TRINIDAD-2475
> URL: https://issues.apache.org/jira/browse/TRINIDAD-2475
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Skinning
> Affects Versions: 2.1.0-core
> Reporter: Anand V Nath
> Priority: Minor
> Attachments: bug-17768650.patch
>
>
> <org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl>
> <ViewHandlerImpl> <_checkTimestamp> <Apache Trinidad is running with
> time-stamp checking enabled. This should not be used in a production
> environment. See the org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION
> property in WEB-INF/web.xml>
> This warning message is logged in non ProjectStage.Production mode also.
> Further we coerce "true" for this parameter in ProjectStage.Development mode,
> which is not correct according to the public documentation here:
> http://myfaces.apache.org/trinidad/devguide/configuration.html
> {quote}
> org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION
> If this parameter is enabled by setting to "true", Apache Trinidad will
> automatically check the modification date of your JSPs and skinning CSS
> files, and discard saved state when they change; this makes development
> easier, but adds overhead that should be avoided when your application is
> deployed. For applications that run in ProjectStage.Production, the value is
> "false" and all other stages use "true" as their default value. However, a
> user can override the ProjectStage behavior by using this flag.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
