I'm late, but +1 as well. On 12/9/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
+1 On 12/9/06, Martin Marinschek <[EMAIL PROTECTED]> wrote: > we should remember to also file a spec CR on this for the next version > of JSF - findComponent and invokeOnComponent could definitely gain > something from this option. > > regards, > > Martin > > On 12/8/06, Adam Winer <[EMAIL PROTECTED]> wrote: > > Alrighty, filed http://issues.apache.org/jira/browse/ADFFACES-325. > > I'll take this on. > > > > -- Adam > > > > > > On 12/8/06, Scott O'Bryan <[EMAIL PROTECTED]> wrote: > > > Well in that case... +1 :) > > > > > > Matthias Wessendorf wrote: > > > > feedback by all is welcome. > > > > > > > > a good community provides good code; > > > > that's Apache ;) > > > > > > > > -M > > > > > > > > On 12/8/06, Böhringer Jochen <[EMAIL PROTECTED]> wrote: > > > >> I'm not a commiter, but I would also raise my hand for the > > > >> > > > >> "::" syntax. > > > >> > > > >> Regards > > > >> Jochen > > > >> > > > >> Von: venkata guddanti [mailto:[EMAIL PROTECTED] > > > >> Gesendet: Freitag, 8. Dezember 2006 18:07 > > > >> An: [email protected] > > > >> Betreff: Re: partialTriggers and naming containers > > > >> > > > >> +1 to "::" syntax. > > > >> > > > >> Can we also enhance the partialTriggers such that if we do not find a > > > >> component inside the naming container, we automatically look > > > >> for it using the parent component? > > > >> > > > >> Of course "::" syntax is more predictable. > > > >> > > > >> Regards, > > > >> Venkata > > > >> > > > >> On 12/8/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > > > >> > > > > >> > > So, to fix this, I'd like to support some extra syntax like ".." > > > >> > > in file paths. I'm thinking "::" to go up a level. Maybe ":::" > > > >> > > to go up two, etc.? So, partialTriggers="::first:foo" would work. > > > >> > > > > > >> > > How's this sound? > > > >> > > > > >> > Interesting idea. A ".." like approach for sorta navigation inside the > > > >> > component tree sounds good for me. > > > >> > > > > >> > I think the problem is the same with the for attribute (like on > > > >> > <message />) when refering to a UIComponent outside of the current NC. > > > >> > > > > >> > To make it short => +1 > > > >> > > > > >> > -M > > > >> > > > > >> > > -- Adam > > > >> > > > > > >> > > > > >> > > > > >> > -- > > > >> > Matthias Wessendorf > > > >> > http://tinyurl.com/fmywh > > > >> > > > > >> > further stuff: > > > >> > blog: http://jroller.com/page/mwessendorf > > > >> > mail: mwessendorf-at-gmail-dot-com > > > >> > > > > >> > > > > > > > > > > > > > > > > > > > -- > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces > -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
