myfaces-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Myfaces Wiki] Update of "Trinidad_goes_ProjectStage" by MatthiasWessendorf
Date Tue, 08 Dec 2009 16:53:29 GMT
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?action=diff&rev1=3&rev2=4

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

   * 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'''''
+ '''''does make sense to port to ProjectStage API'''''
  
  == The trinidad-config.xml file ==
  See here for infos about it:
@@ -66, +66 @@

   * <debug-output> (from trinidad-config.xml file)
    * '''Production''' => FALSE 
    * '''other stages''' => TRUE
+  * org.apache.myfaces.trinidad.CHECK_STATE_SERIALIZATION (System Property)
+   * '''Production''' => NONE
+   * '''Development and UnitTest''' => SESSION,TREE 
+   * '''SystemTest''' => ALL 
+ 
  
  == 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.

Mime
View raw message