[ http://issues.apache.org/jira/browse/TAPESTRY-860?page=comments#action_12451875 ] Andy Yeung commented on TAPESTRY-860: -------------------------------------
I have try using a simple integer and a collection as persist property. the collection property even fail to clean up for the new value in new session. All users now share the same collections property in the page pool. > SessionPropertyPersistenceStrategy Does Not Recognize Changes to Collections > ---------------------------------------------------------------------------- > > Key: TAPESTRY-860 > URL: http://issues.apache.org/jira/browse/TAPESTRY-860 > Project: Tapestry > Issue Type: Bug > Components: Framework > Affects Versions: 4.0 > Reporter: Jeremy F. Kassis > Priority: Minor > > Create a page property as follows: > <property name="foo" persist="session">new java.util.HashSet()</property> > In a listener method, add an item to the collection. The > SessionPropertyPersistenceStrategy does not record the change. > Workaround: Resave the collection using the setter. However, when a page > passes a persistent collection property to a subcomponent, the subcomponent > must know to resave the collection using the setter to "hack" the Tapestry > functionality. This breaks an abstraction barrier between page and component. > Anyway, there you have it. -- 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]
