[TRINIDAD-2060] Make Optimized PPR the default with a public flag to disable it at the web.xml and application levels

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.0.0-core
• Fix Version/s: 2.0.0-core
• Assignee: Blake Sullivan
• Reporter: Blake Sullivan
• Created: 11/Mar/11 00:48
• Updated: 11/Mar/11 01:18
• Resolved: 11/Mar/11 01:18

Description

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