I ran into this situation on a couple of my pages that had <c:choose>
statements on them.
The solution for me was to put the same number of JSF components in each
of the <c:when> clauses. So if one clause really needed a JSF tag, and
the other did not, I just added a <h:outputText> to output the empty
string in the second clause. This way, the clauses all have the same
number of JSF components, and the components that come *after* them on
the page get the same spots on the component tree.
I also had to make sure that all of my components in <c:when> clauses
had explicitly assigned ids, not auto.
This lets me change the structure of the page and redisplay it all I
want, without navigating elsewhere. I have been using this workaround
for months, without any further problems.
Don't know if this applies to the page restructuring you are doing, but
I hope it helps.
Regards,
Jeff Bischoff
Kenneth L Kurz & Assoc, Inc.
octoberdan wrote:
Actually, all you need is to navigate away from the page and then back to the
page.
--
View this message in context:
http://www.nabble.com/Client-id-%3A-...-is-duplicated-in-the-faces-tree.-t1712357.html#a4684867
Sent from the MyFaces - Users forum at Nabble.com.
