I recently discovered the same problem with the tree2 component (http://issues.apache.org/jira/browse/MYFACES-580).
It seems that this problem is caused by a call to context.getViewRoot().createUniqueId() within the component renderer.
I changed the renderer so that it does not depend on this method. And the problem seems to be gone.
Maybe the jscookmenu does something similar ... somehow corrupting the component tree.
May be a more general bug.
[EMAIL PROTECTED] schrieb am 20.09.2005 15:13:45:
> Hi!
>
> its me again, another problem after moving from 1.0.9m9 to 1.1.0. With
> the same application running fine in 1.0.9m9, I get the following
> exception when a page reloads:
>
> 2005-09-20 15:06:47,753 ERROR [jsp]: Servlet.service() for servlet jsp
> threw exception
> javax.faces.FacesException: cannot add component with id '_id21' and
> path : {Component-Path : [Class:
> javax.faces.component.html.HtmlInputText,Id: _id21]} to its parent
> component.
> This might be a problem due to duplicate ids.
> at
> javax.faces.webapp.UIComponentTag.findComponent(UIComponentTag.java:401)
> at
> javax.faces.webapp.UIComponentTag.doStartTag(UIComponentTag.java:219)
> at
> org.apache.jsp.templates.generic_jsp._jspx_meth_h_inputText_1(org.
> apache.jsp.templates.generic_jsp:1642)
> at
> org.apache.jsp.templates.generic_jsp._jspx_meth_h_panelGrid_4(org.
> apache.jsp.templates.generic_jsp:1598)
> at
> org.apache.jsp.templates.generic_jsp._jspService(org.apache.jsp.
> templates.generic_jsp:636)
> at
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
> org.apache.jasper.servlet.JspServletWrapper.
> service(JspServletWrapper.java:322)
> at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:291)
> at
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
>
> I search the mailing list and someone suggested to assign a id by hand
> to every component - which is much work and would clumber the jsf pages.
>
> I manualy added a id to the component with the duplicate id and
> redeployed the app - now I get the exception from another component. So
> what changed from 1.0.9m9 to 1.1.0 related to this problem?
>
>
> Another strange thing is that I get the following warning:
>
> 2005-09-20 15:06:39,481 INFO [/XXX]: WARNING: Component _id12 just got
> an automatic id, because there was no id assigned yet. If this component
> was created dynamically (i.e. not by a JSP tag) you should assign it an
> explicit static id or assign it the id you get from the createUniqueId
> from the current UIViewRoot component right after creation!
>
> The only thing I create dynamically are the menu items for the
> jscookmenu.... may these cause the problem?
