[ http://issues.apache.org/jira/browse/TAPESTRY-437?page=comments#action_12318863 ]
Cherry Development commented on TAPESTRY-437: --------------------------------------------- I've verified that this simple change DOES, in fact, fix the problem. I would even suggest that this problem is more than just minor priority. It effectively makes the Select component broken. I've had to patch my own local copy in order to be able to use it. > Select component exception when used twice on a page > ---------------------------------------------------- > > Key: TAPESTRY-437 > URL: http://issues.apache.org/jira/browse/TAPESTRY-437 > Project: Tapestry > Type: Bug > Components: Framework > Versions: 4.0 > Reporter: Nick Westgate > Priority: Minor > > From tapestry users thread "Is there a bug for dual Select components?" > Exception is "Select components may not be nested." > Caused by changes to Select in T4.0 omitting > "cycle.removeAttribute(ATTRIBUTE_NAME);" > Suggested fix in Select.java - add the following line (+++) > protected void cleanupAfterRender(IRequestCycle cycle) > { > _rendering = false; > _selections = null; > ++++ cycle.removeAttribute(ATTRIBUTE_NAME); > } -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
