It's not always obvious which components in Trinidad are naming containers, so I was thinking it'd be good to add naming container information to our tagdoc:
For example, we currently have: Tag name: <tr:breadCrumbs> UIComponent class: org.apache.myfaces.trinidad.component.core.nav.CoreBreadCrumbs Component type: org.apache.myfaces.trinidad.CoreBreadCrumbs but could autogenerate: Tag name: <tr:breadCrumbs> UIComponent class: org.apache.myfaces.trinidad.component.core.nav.CoreBreadCrumbs Component type: org.apache.myfaces.trinidad.CoreBreadCrumbs Naming container: yes, when identifying a child, you must include its ID in partialTriggers, calls to findComponent() etc. Sound good? -- Adam
