[ http://issues.apache.org/jira/browse/MYFACES-769?page=comments#action_12360185 ]
Dave Brondsema commented on MYFACES-769: ---------------------------------------- Java code is not used to create the component tree, but that doesn't matter. I don't know if it affects servlet JSF apps. Imagine a jsp file that is included twice on the same page. If the component ids are the same both times, then it is a problem. I suspect it is not. Back to portlets. Whether ids are defined explicitly or not, the problem occurs. This is because the first time the portlet is run, the components have (for example) ids A, B, and C. When the portlet is displayed a second time on the page the components again have ids A, B, and C. The resulting aggregated HTML has A, B, and C twice. There needs to be a way to have dynamic ids for the rendered HTML. I hope that made sense. > configurable IDs used for rendering > ----------------------------------- > > Key: MYFACES-769 > URL: http://issues.apache.org/jira/browse/MYFACES-769 > Project: MyFaces > Type: Improvement > Reporter: Dave Brondsema > > 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
