[
https://issues.apache.org/jira/browse/TRINIDAD-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13005435#comment-13005435
]
Blake Sullivan commented on TRINIDAD-2060:
------------------------------------------
The name of the property will be "org.apache.myfaces.trinidad.PPR_OPTIMIZATION"
> Make Optimized PPR the default with a public flag to disable it at the
> web.xml and application levels
> -----------------------------------------------------------------------------------------------------
>
> Key: TRINIDAD-2060
> URL: https://issues.apache.org/jira/browse/TRINIDAD-2060
> Project: MyFaces Trinidad
> Issue Type: Improvement
> Affects Versions: 2.0.0-beta-3
> Reporter: Blake Sullivan
> Assignee: Blake Sullivan
> Priority: Minor
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Optimized PPR is currently enabled using the internal web.xml
> flag:"org.apache.myfaces.trinidadinternal.ENABLE_PPR_OPTIMIZATION" to enable
> PPR Optimization in web.xml and the following internal application map
> property "org.apache.myfaces.trinidadinternal.DISABLE_PPR_OPTIMIZATION" to
> dynamically turn PPR optimization on and off.
> PPR Optimization currently defaults off
> The proposal is to:
> 1) Make PPR Optimization default to "on" now that we've tested the components
> and fixed the tree visiting bugs
> 2) Support a public flag in case an application is working with a third party
> component that doesn't support PPR optmization
> 3) Make the application and web.xml flags the same to avoid confusion (the
> application flag is useful for debugging)
> 4) Use the value "on" and "off" in case we need to add a third value later
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
