+1: I think it is a very common problem that people run into. Sure you can look up the component class being used by the tag and then find its JavaDoc and then look at the top to see if it contains NamingContainer but being such a common task, I think it would be very helpful to indicate in the tag docs.
Thank you, Matt On 7/17/07, Simon Lessard <[EMAIL PROTECTED]> wrote:
+0. On one side, this would directly link the tag with the component class. I know there isn't much chance that it would change, but wasn't it the point of component type to indirect such info ? On the other hand though, I'd find that info useful, because I wouldn't have to browse the component API doc to see what interfaces are implemented. Regards, ~ Simon On 7/17/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > > why not, > the "more" documentation, the better :-) > > On 7/17/07, Adam Winer <[EMAIL PROTECTED]> wrote: > > 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 > > > > > -- > Matthias Wessendorf > > further stuff: > blog: http://matthiaswessendorf.wordpress.com/ > mail: matzew-at-apache-dot-org >
