Affects Version/s: 1.1.15
Fix Version/s: None
JSF 2.0 RI
There seems to be a problem with the algorithm that assigns tag ids. Say we have the following code:
where ns is some namespace and compositeComponent is a component defined in its own file:
The implementation of Bean (session scoped in my case):
After clicking on the command link the exception is thrown:
Component ID form:bb has already been found in the view.
The problem is that during the process of building view after the click, the generated id for the first <h:panelGroup> component (inside <c:if>) is exactly the same as it was for the second <h:panelGroup> during the first tree building process. This way during the second tree building process the first <h:panelGroup> component is found and the second (the one outside <c:if>) - was not found, therefore the second one is created and assigned JSF id "bb". This way we have two <h:panelGroup> components with id="bb"