[Myfaces Wiki] Update of "Trinidad_goes_ProjectStage" by MatthiasWessendorf

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Myfaces Wiki" for change notification.

The "Trinidad_goes_ProjectStage" page has been changed by MatthiasWessendorf.
http://wiki.apache.org/myfaces/Trinidad_goes_ProjectStage

--------------------------------------------------

New page:
In order to adopt the JSF 2.0 standard for Trinidad, we have to introduce the ProjectStage API and should use it, where it actually makes sense.

= list of all Trinidad configuration parameters =

== System Properties ( => System.getProperty(....)) ==
 * org.apache.myfaces.trinidad.CHECK_STATE_SERIALIZATION
documentation is here:
 * http://issues.apache.org/jira/browse/TRINIDAD-1245
 * http://myfaces.apache.org/trinidad/trinidad-api/apidocs/org/apache/myfaces/trinidad/bean/util/StateUtils.html

'''''does not really make sense to port to Stage'''''

== The trinidad-config.xml file ==
See here for infos about it:
 * http://myfaces.apache.org/trinidad/devguide/configuration.html

I think that '''''ONLY''''' this element could make sense:
 * <debug-output> (e.g. as for PRODUCTION you want FALSE here... )

== Settings in the WEB.XML (aka Context Parameters) ==
Some info is here as well:
 * http://myfaces.apache.org/trinidad/devguide/configuration.html

The web.xml has different types of settings (some fit to ProjectStage, some not)

Here is a grouped list, where I think they '''''do not''''' make sense with project_stage at all:
 * org.apache.myfaces.trinidad.CACHE_VIEW_ROOT
 * org.apache.myfaces.trinidad.CLIENT_STATE_METHOD
 * org.apache.myfaces.trinidad.CLIENT_STATE_MAX_TOKENS
 * org.apache.myfaces.trinidad.CHANGE_PERSISTENCE
 * org.apache.myfaces.trinidad.USE_APPLICATION_VIEW_CACHE
 * org.apache.myfaces.trinidad.ENABLE_LIGHTWEIGHT_DIALOGS
 * org.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER
 * org.apache.myfaces.trinidad.FACELETS_VIEW_MAPPINGS
 * org.apache.myfaces.trinidad.UPLOAD_MAX_MEMORY
 * org.apache.myfaces.trinidad.UPLOAD_MAX_DISK_SPACE
 * org.apache.myfaces.trinidad.UPLOAD_TEMP_DIR

These parameters do '''''make sense''''':
 * org.apache.myfaces.trinidad.DEBUG_JAVASCRIPT
 * org.apache.myfaces.trinidad.DISABLE_CONTENT_COMPRESSION
 * org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION
 * org.apache.myfaces.trinidad.resource.DEBUG

This parameter '''''may''''' make sense ('''''caution:'''''  it is an internal and temporary param):
 * org.apache.myfaces.trinidadinternal.ENABLE_PPR_OPTIMIZATION (See http://issues.apache.org/jira/browse/TRINIDAD-1368)

== List of valid candidates for ProjectStage API ==
 * org.apache.myfaces.trinidad.DEBUG_JAVASCRIPT
 * org.apache.myfaces.trinidad.DISABLE_CONTENT_COMPRESSION
 * org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION
 * org.apache.myfaces.trinidad.resource.DEBUG
 * org.apache.myfaces.trinidadinternal.ENABLE_PPR_OPTIMIZATION (see above)
 * <debug-output> (from trinidad-config.xml file)

== Overriding single settings ==
Perhaps we want to be able to still override settings, regardless for the current STAGE. Means: If the application runs in "ProjectStage.Production", we do CSS ompression. BUT... if the web.xml says "org.apache.myfaces.trinidad.DISABLE_CONTENT_COMPRESSION => TRUE", we should honor that... This would give users a more fine grained control over these configuration settings.