[ http://issues.apache.org/jira/browse/MYFACES-509?page=comments#action_12322804 ]
Martin Marinschek commented on MYFACES-509: ------------------------------------------- We ought to check for clientIds, not ids. What was wrong was that a clientId of null was not accepted - of course it should be as the RI does ;) If we check for ids, we would need to remember naming containers and compare only the children of naming containers to each other. Would be possible to, but it should work as implemented as well, even though going through the naming containers might be more performant. regards, Martin > StateManager.saveSerializedView must throw an IllegalStateException when View > contains duplicate IDs > ---------------------------------------------------------------------------------------------------- > > Key: MYFACES-509 > URL: http://issues.apache.org/jira/browse/MYFACES-509 > Project: MyFaces > Type: Bug > Components: JSR-127 > Versions: 1.0.9m9 > Reporter: Bruno Aranda > Assignee: Martin Marinschek > Fix For: Nightly Build > > Acording to the javadocs, the method StateManager.saveSerializedView must > throw an IllegalStateException if more than one component or facet within the > same NamingContainer in this view has the same non-null component id. -- 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
