> 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).
Yes but the renderer handles the reconstruction of the compoenent tree (at least the updating of the components with the form data.) So we are all in agreement that the JSF spec does not technically require unique ids for *every* component in the tree? This was the first point I was trying to argue. I wasn't sure myself, but Craig seems to have settled this one. I agree that UIComponentBase should be left alone (and this is how I've implemented it for now.) My only point is that since JSF doesn't really require the id's to be unique throughout the entire tree, that requirement is probably best handled through the renderer (if possible which its not right now) because only XHTML cares about this requirement. Probably not much use in us debating this further since I only disagree with you in theory. Unfortunately the reality is that the solution I think is best is not possible right now. > -Heath Borders-Wing sean
