Return-Path: Delivered-To: apmail-myfaces-dev-archive@www.apache.org Received: (qmail 91938 invoked from network); 8 Dec 2009 16:57:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 8 Dec 2009 16:57:23 -0000 Received: (qmail 74550 invoked by uid 500); 8 Dec 2009 16:57:23 -0000 Delivered-To: apmail-myfaces-dev-archive@myfaces.apache.org Received: (qmail 74382 invoked by uid 500); 8 Dec 2009 16:57:22 -0000 Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Development" Delivered-To: mailing list dev@myfaces.apache.org Received: (qmail 74374 invoked by uid 99); 8 Dec 2009 16:57:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Dec 2009 16:57:21 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mwessendorf@gmail.com designates 209.85.219.225 as permitted sender) Received: from [209.85.219.225] (HELO mail-ew0-f225.google.com) (209.85.219.225) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Dec 2009 16:57:09 +0000 Received: by ewy25 with SMTP id 25so4833625ewy.25 for ; Tue, 08 Dec 2009 08:56:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=Lfc91Dc/2QrgdCUnaEJnMfZHGpK9P4mql/A4mZsX8EQ=; b=TFCBLaIOo7wg6J7sOV2lKjpQJV/zQaBdTc1H0mekVXyHrKHc41DXDnqoknTpfB4su2 YGdkkMKyHSuZwMWjUM6Wjl/XtZ2a4LW/a784LOSmJcXpPEpp98Ak/hZ5Bw/ypcMMzAhL sn6BiuaQa4dxTQD5g7p106BWnPoQqRLEKCglE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=IhfhlGehMZDuJyT0Gn2FdqkVO9mXISEpQca6VfJjHfCmGY1C/TboOfDSaOhxG0agsF jzIRQRZ/OCUOaFF/xyjC2OtkMsF9eNr15PkJk0DDUFlBcTssvdTdmo8DhQdo8rWSSMF6 9zqhtRrHubgPfFEZgoNrushngl+EoFCVmxAJY= MIME-Version: 1.0 Sender: mwessendorf@gmail.com Received: by 10.216.86.201 with SMTP id w51mr2897084wee.8.1260291409305; Tue, 08 Dec 2009 08:56:49 -0800 (PST) In-Reply-To: <71235db40912080854k40c19198l1e9657f3c088726d@mail.gmail.com> References: <71235db40912020025r2225d159sc076a70aa0cf8057@mail.gmail.com> <1259756677.4487.79.camel@markoc-desktop> <71235db40912020618h2ada7306x5918250c10985971@mail.gmail.com> <71235db40912021043j4ba3dfbco8d0c226557e9c9c2@mail.gmail.com> <4B16C587.7010805@oracle.com> <71235db40912021206n322e9287t6f6106be3622c2de@mail.gmail.com> <71235db40912080854k40c19198l1e9657f3c088726d@mail.gmail.com> Date: Tue, 8 Dec 2009 17:56:48 +0100 X-Google-Sender-Auth: d2ffe91bfb6deca3 Message-ID: <71235db40912080856v21cdc1e1jbe47ce49b874c540@mail.gmail.com> Subject: Re: [Trinidad 2.0] introducing ProjectStage API From: Matthias Wessendorf To: MyFaces Development Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org http://wiki.apache.org/myfaces/Trinidad_goes_ProjectStage On Tue, Dec 8, 2009 at 5:54 PM, Matthias Wessendorf wro= te: > ok, > > I updated the wiki: > > I will continue with these values, as there was no concern against them. > > regarding the hidden, unspecified > "javax.faces.FACELETS_REFRESH_PERIOD" parameter, I will follow up in > a different thread. > > -Matthias > > On Wed, Dec 2, 2009 at 9:06 PM, Matthias Wessendorf w= rote: >> On Wed, Dec 2, 2009 at 8:52 PM, Pavitra Subramaniam >> wrote: >>> "Matthias Wessendorf wrote:" On 12/2/2009 10:43 AM PT: >>> >>> Ok, >>> >>> I added some value suggestions to those guys that we identified to fit >>> into the ProjectStage API: >>> >>> >>> -org.apache.myfaces.trinidad.DEBUG_JAVASCRIPT >>> =C2=A0* Production =3D> FALSE >>> =C2=A0* other stages =3D> TRUE >>> >>> >>> +1. although I think if a user were to change the recommended defaults,= like >>> set ProjectStage=3DProduction and override the DEBUG_JS to be true, the= n we at >>> least need to warn the user of this as appropriate. >> >> Yeah I was planing do WARNING for everything that is overridden >> >>> >>> -org.apache.myfaces.trinidad.DISABLE_CONTENT_COMPRESSION >>> =C2=A0* Production =3D> FALSE >>> =C2=A0* other stages =3D> TRUE >>> -org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION >>> =C2=A0* Production =3D> FALSE >>> =C2=A0* other stages =3D> TRUE >>> -org.apache.myfaces.trinidad.resource.DEBUG >>> =C2=A0* Production =3D> FALSE >>> =C2=A0* other stages =3D> TRUE >>> -org.apache.myfaces.trinidadinternal.ENABLE_PPR_OPTIMIZATION (see above= ) >>> =C2=A0* Production =3D> FALSE (current default) >>> =C2=A0* other stages =3D> TRUE >>> - (from trinidad-config.xml file) >>> =C2=A0* Production =3D> FALSE >>> =C2=A0* other stages =3D> TRUE >>> >>> >>> +1. I also was wondering if >>> "org.apache.myfaces.trinidad.CHECK_STATE_SERIALIZATION" should be set t= o >>> NONE in Production if this is really used for a testing Trinidad in >>> pseudo-High Availability (HA) mode. It looks like we could set this >>> different values based on the the ProjectStage >>> >>> Production >>> org.apache.myfaces.trinidad.CHECK_STATE_SERIALIZATION=3Dnone >>> >>> Development, Unit Test >>> org.apache.myfaces.trinidad.CHECK_STATE_SERIALIZATION=3Dsession,tree >>> >>> System Test >>> org.apache.myfaces.trinidad.CHECK_STATE_SERIALIZATION=3Dall >> >> great. thanks for the feedback. Makes sense to me. I think that this >> parameter actually *translates* to the ProjectStage. >> Your suggestions make sense to me. >> >> -Matthias >> >> >>> >>> -Pavitra >>> >>> Please let me know what you think... >>> >>> >>> I updated the wiki page, to reflect the suggestions: >>> http://wiki.apache.org/myfaces/Trinidad_goes_ProjectStage >>> >>> I also created this JIRA ticket, to keep track of the item: >>> https://issues.apache.org/jira/browse/TRINIDAD-1652 >>> >>> -Matthias >>> >>> On Wed, Dec 2, 2009 at 3:18 PM, Matthias Wessendorf >>> wrote: >>> >>> >>> yep, that's what I was saying >>> >>> On Wed, Dec 2, 2009 at 3:04 PM, Jakob Korherr >>> wrote: >>> >>> >>> Hi, >>> >>> I think the best way would be that the init parameters have stage relat= ed >>> standard values (actually that what Matthias suggested), for example: >>> >>> If we are in ProjectStage.Production the standard value of >>> org.apache.myfaces.trinidad.DISABLE_CONTENT_COMPRESSION is false, other= wise >>> it is true. >>> >>> But this only sets the DEFAULT value. The user still can configure each >>> parameter independently by putting it in web.xml. >>> >>> Regards >>> >>> Jakob Korherr >>> >>> 2009/12/2 Martin Koci >>> >>> >>> Hi, >>> >>> does trinidad reload both JSP and facelets views if >>> org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION=3Dtrue? >>> >>> For facelets based views there is a new JSF 2.0 param >>> javax.faces.FACELETS_REFRESH_PERIOD (-1 =3D never reload, 0=3Dalways, 1= ,2, >>> 3,.. - check interval) but it's relation to project stage is not clear = - >>> see https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=3D1434 >>> >>> Martin Ko=C4=8D=C3=AD >>> >>> Matthias Wessendorf p=C3=AD=C5=A1e v St 02. 12. 2009 v 09:25 +0100: >>> >>> >>> Hi, >>> >>> here is a (complete?) list of all Trinidad configuration parameters: >>> >>> * System Properties ( =3D> 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/myfa= ces/trinidad/bean/util/StateUtils.html >>> >>> =3D=3D> 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: >>> - >>> (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 don't 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 >>> (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): >>> -org.apache.myfaces.trinidadinternal.ENABLE_PPR_OPTIMIZATION >>> See http://issues.apache.org/jira/browse/TRINIDAD-1368 >>> >>> So basically, only these make sense (for me): >>> -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) >>> - >>> >>> 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 =3D> TRUE", >>> we should honor that... This would give users a more fine grained >>> control over these configuration settings. >>> >>> What do you think ? >>> >>> Greetings, >>> Matthias >>> >>> >>> >>> >>> >>> >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >>> >>> >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > --=20 Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf