Return-Path: Delivered-To: apmail-myfaces-dev-archive@www.apache.org Received: (qmail 43490 invoked from network); 11 Nov 2009 17:17:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 11 Nov 2009 17:17:13 -0000 Received: (qmail 87028 invoked by uid 500); 11 Nov 2009 17:17:13 -0000 Delivered-To: apmail-myfaces-dev-archive@myfaces.apache.org Received: (qmail 86944 invoked by uid 500); 11 Nov 2009 17:17:13 -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 86936 invoked by uid 99); 11 Nov 2009 17:17:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Nov 2009 17:17:13 +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 andrew.rw.robinson@gmail.com designates 209.85.222.192 as permitted sender) Received: from [209.85.222.192] (HELO mail-pz0-f192.google.com) (209.85.222.192) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Nov 2009 17:17:04 +0000 Received: by pzk30 with SMTP id 30so921789pzk.24 for ; Wed, 11 Nov 2009 09:16:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=oVWLAIDcFNO/Pr3sK0dV1dxVSk5YrBlTaHsDSSwW9ps=; b=U5mfa05Kxnn6N8DDsvznAfzgAS77FXxKqQPaXObqZrlCa5llhYPYPoQ7Rfa8WYUUnJ /bEHn1rXgKdywKX9m19SuG1lN40IvlBxtMsZ/tQVtM+wv9qo7Tj4Zi1V8+4Zmcv9z4yb h+XooG9d9RdoNqyDXRy34lVcXpVUy+sIvp6r8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=iyiL35/dRW+6cyowUKO6PHjzExm7KYdLCTDK24HjycqvNxfC9OaBrSEWoUNmzIUeLo AneL02UIs+Zb6JafY11M29nb7hyKLn1vWDGv2+nRSfgxh6Vb1h9CsIW0rBYl2JOrokWV onhimkL8JMeR36PDcH7BIy4JPyfAUzJc6Fg3k= MIME-Version: 1.0 Received: by 10.142.67.7 with SMTP id p7mr195081wfa.251.1257959803683; Wed, 11 Nov 2009 09:16:43 -0800 (PST) In-Reply-To: References: Date: Wed, 11 Nov 2009 10:16:43 -0700 Message-ID: Subject: Re: [Trinidad] Okay to deprecate ComponentUtils.findRelativeComponent and move the code under the control of UIXComponent? From: Andrew Robinson To: MyFaces Development Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Note that the deprecated syntax was done as part of https://issues.apache.org/jira/browse/TRINIDAD-757 So it has been deprecated since Oct 2007 -Andrew On Wed, Nov 11, 2009 at 10:05 AM, Andrew Robinson wrote: > Added a JIRA issue for this: TRINIDAD-1633 > > In addition to just moving it I would like to remove the support for > the deprecated syntax that we have been keeping around as it would not > fit as nicely. This deprecated syntax was the one in which the "::" > was not necessary to search in the parent naming container from a > naming container. It did not match the paradigm for the findComponent > API, so we changed it a couple of years back or so. I think that this > is adequate time to have migrated the projects over, but please let me > know if there are any strong objects to removing this support. > > Thanks, > Andrew > > On Tue, Nov 10, 2009 at 4:59 PM, Andrew Robinson > wrote: >> With looking forward to JSF2 and the composite component design, there >> are some instances where we may want to control how the "::" gets >> resolved at the component level. This would be useful for relocated >> facets so that the user's original "::" would be correctly interpreted >> from the original page location. >> >> What I would like to do is to move the code from >> ComponentUtils.findRelativeComponent to UIXComponent as a static >> public method "public static String findComponent(UIComponent >> component, String id)". Then UIXComponent would also provide built in >> support for "::" in the findComponent instance method. The reason for >> the static method is so the UIXComponent.findComponent could be used >> to achieve the relative (::) find strings to use with non-UIXComponent >> components. The implementation would be to have UIXComponent handle >> the resolution of the colons in the static method for UIComponent >> instances, and delegate the code to the instance method for >> UIXComponent instances. Basically, the same design pattern as the code >> I added to UIXComponent for the addPartialTarget method. >> >> ComponentUtils.findRelativeComponent would be then deprecated and >> simply call UIXComponent.findComponent (static). >> >> Are there any objections to this change? >> >> Thank you, >> Andrew >> >