[ http://issues.apache.org/jira/browse/MYFACES-978?page=comments#action_12361262 ]
Martin Marinschek commented on MYFACES-978: ------------------------------------------- Well, upon reflection we may not save the state of the uniqueIdCounter even if this is less than optimal. I have reverted the patch. The thing is that the count needs to start anew on each request cause this count is not actually a unique counter for component instances, but for JSP-tag-instances... JSF1.2 will solve this in a better way. regards, Martin > tree2 affected by changes to UIViewRoot > --------------------------------------- > > Key: MYFACES-978 > URL: http://issues.apache.org/jira/browse/MYFACES-978 > Project: MyFaces > Type: Bug > Components: Tomahawk > Versions: Nightly > Environment: nightly builds from dec. 22, 23 - tomcate 5.5 > Reporter: Dennis Byrne > Priority: Minor > > 1.) Build and deploy the latest simple.war > 2.) go the the tree2 (nice wrap) demo. > 3.) click on the only rendered node. > 4.) form submits, the action does fire, but tree2 is not rendered > The tree will render however if you explictly set the id of the tree's parent > element, a panelgrid. The same behavior holds true if the parent element is > h:form (tree renders w/ explicit [EMAIL PROTECTED], does not render w/out > [EMAIL PROTECTED]). > This behavior is not seen w/ builds of myFaces-all.jar before dec. 23. I > also do not get this problem after checking out trunk, and doing a build > after manually rolling back the latest change to UIViewRoot. This (harmless > looking) change happened on the 23rd. > This does not happen using client side toggle. -- 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
