Hello!
I think that the component tree get confused by a component, maybe
jscookmenu, because after I assigned a fixed id to the component I get
the "duplicate id" for, another id is reported.
What I will do today is strip down the page so I can definitively say
which component causes the problem.
Mathias Brökelmann wrote:
the JSP spec don´t allow components with the same id within the same
namingcontainer.
The menu items could be a problem if you add the same component
instance to different parents (which breaks the component tree -
because a component instance may only have one parent).
2005/9/20, Boris Klug <[EMAIL PROTECTED]>:
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?
