Again, the renderer doesn't need to solve this problem because it also concerns the how the tree is reconstructed. It is not just an (X)HTML problem. That's why the checking code should stay within the getClientId(FacesContext) method on the individidual UIComponents (but not on UIComponentBase because this behavior is not specified by the API).
On Mon, 10 Jan 2005 15:10:54 -0500, Sean Schofield <[EMAIL PROTECTED]> wrote: > > Yes, that's ok ... it is the *client* ids that have to be unique, > > which is (in turn) why the default mechanism for calculating client > > ids concatenates them together when the parent component is a > > NamingContainer (as subview is). > > So would you agree with my position that ideally the renderer enforce > this instead of ComponentBase or something tied to the JSF components? > (Also, just to clarify this would be how I would like to do this, not > how I am doing it now.) > > > Craig > > sean > -- -Heath Borders-Wing [EMAIL PROTECTED]
