yeah, I am in that boat as well. clearer. -Matthias
On Jan 31, 2008 11:37 PM, Jeanne Waldman <[EMAIL PROTECTED]> wrote: > I like this solution because it is much clearer to me. I would like to > know/investigate what someone would have to change in his jspx file > between this solution and the original solution (before the bug was fixed). > > Is it only if the partialTriggers were on a naming container and it is > looking for its children? > > In your example, it is easy for the table to set the partialTrigger of > his children: > > <f:subview id="A"> > <tr:commandButton id="B" /> > <tr:table id="C" partialTriggers="::B E G ::H:I:K ::H:N"> > <tr:column id="D"> > <tr:commandButton id="E" /> > <tr:inputText partialTriggers="::B E G ::C ::H:I:K ::H:N" /> > </tr:column> > <tr:column id="F"> > <tr:commandButton id="G" /> > </tr:column> > </tr:table> > > with the OLD solution where we started with the parent component we > wouldn't be able to say E or G on table, correct? Instead we'd have to > say ::C:E and ::C:G? > Is that correct? > > - Jeanne > > > > Leonardo Uribe wrote: > > +1 , use string arrays to use multiple partial triggers makes that the > > logic of the page be in 2 places, so this solution is good > > > > > -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf mail: matzew-at-apache-dot-org
