UIComponentBase.findComponent does not allow use the same id for a child component.

Suppose the following tree

x

and the following search expression:

x:x

The current algorithm has at the end this line:

return findBase.findComponent(expr.substring(separator + 1));

The effect of this call is the component is not found, because the first x is swallowed, but the recursive call over the same component return the parent again, so the expected component is not returned, instead the parent.

It is rare to use this kind of code, but with composite components, there are NamingContainer instances everywhere, which makes this issue more probable.