myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthias Wessendorf <>
Subject [Trinidad 2.0] introducing ProjectStage API
Date Wed, 02 Dec 2009 08:25:24 GMT

here is a (complete?) list of all Trinidad configuration parameters:

* System Properties ( => System.getProperty(....)):
documentation is here:

==> does not really make sense to port to Stage.....

* The "trinidad-config.xml" file:
See here for infos about it:

I think that ONLY this element could make sense:
(e.g. as for PRODUCTION you want FALSE here... )

* Settings in the WEB.XML (aka Context Parameters):
Some info is here as well:

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

Here is a grouped list, where I think they don't make sense with
project_stage at all:

These parameters do make sense:
(note, we need a bug here, as this is NOT documented in the "official
documentation" :-) )

This parameter _may_ make sense (*caution:* it is an internal and
temporary param):

So basically, only these make sense (for me):
-org.apache.myfaces.trinidadinternal.ENABLE_PPR_OPTIMIZATION (*see above)

Let me know if you agree with this list and I will follow up on what
values they should have,
in what STAGE....

A note: Perhaps we want to be able to still override a _SINGLE_
setting, regardless for the
current STAGE. Means: If the application runs in
"ProjectStage.Production", we do CSS compression.
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.

What do you think ?


Matthias Wessendorf


View raw message