On 10/8/07, Andrew Robinson <[EMAIL PROTECTED]> wrote: > > My recommendation is to change the code and documentation to: > > - If the component is a naming container, search relative to the > > parent; otherwise search relative to the component > > But what if the person does want to search the children? If the parent > was used, they would have to refer to themselves, which is more > confusing IMO.
I agree, that's confusing. But, IMO, I think that requiring "::" for finding peers: <af:commandLink id="foo" .../> <af:table partialTriggers="::foo">...</af:table> is also really confusing, and suspect that searching for peers is much more common than searching for children. Plus, it's existing behavior, and breaking existing behavior is never a good thing. -- Adam > Example: > > <my:namingContainer partialTriggers="link"> > <tr:commandLink id="link" partialSubmit="true" /> > </my:namingContainer> > > versus: > > <my:namingContainer id="nc" partialTriggers="nc:link"> > <tr:commandLink id="link" partialSubmit="true" /> > </my:namingContainer> > > So, if it was left as-is in terms of documentation, the following > would be the correct way to refer to a child and refer to a sibling: > > <tr:commandLink id="outsideLink" /> > <my:namingContainer partialTriggers="link, ::outsideLink"> > <tr:commandLink id="link" partialSubmit="true" /> > </my:namingContainer> > > That seems to make sense to me at least > > -Andrew >
