[ http://issues.apache.org/jira/browse/MYFACES-769?page=comments#action_12367734 ]
Dave Brondsema commented on MYFACES-769: ---------------------------------------- Namespaces are definitely the solution to this problem. Sorry I was in left field for a while until I realized this. The portlet container I am using is providing a good namespace, and it is used in some components, but not others. It seems that when I specify the id on the component, it does not use the namespace, but when the id is automatically assigned it does use the namespace. This is of particular importance for my <h:form id="foo" ... > which renders as <form id="foo" name="foo" ...> Why do I need to make sure that the parent-most naming-container in my app has a dynamic id? > configurable IDs used for rendering > ----------------------------------- > > Key: MYFACES-769 > URL: http://issues.apache.org/jira/browse/MYFACES-769 > Project: MyFaces Core > Type: Improvement > Reporter: Dave Brondsema > Assignee: Martin Marinschek > > If the same code is used ot generated a component tree for more than one part > of a webpage, the rendered IDs are the same and functionality is broken > (javascript needs unique IDs). > An example of when this happens is when as portlet uses JSF for rendering. > If the portlet is used more than once on a single page (e.g. an RSS reader) > all the IDs are the same. > Thus we need a way to have more configurable (perhaps random) IDs when > rendered. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
