You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Marcus Schulte (JIRA)" <de...@tapestry.apache.org> on 2008/09/10 19:43:48 UTC
[jira] Updated: (TAPESTRY-860) SessionPropertyPersistenceStrategy
Does Not Recognize Changes to Collections
[ https://issues.apache.org/jira/browse/TAPESTRY-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Schulte updated TAPESTRY-860:
------------------------------------
Fix Version/s: (was: 4.1.6)
4.1.7
> SessionPropertyPersistenceStrategy Does Not Recognize Changes to Collections
> ----------------------------------------------------------------------------
>
> Key: TAPESTRY-860
> URL: https://issues.apache.org/jira/browse/TAPESTRY-860
> Project: Tapestry
> Issue Type: Bug
> Components: Framework
> Affects Versions: 4.0
> Reporter: Jeremy F. Kassis
> Assignee: Jesse Kuhnert
> Priority: Minor
> Fix For: 4.1.7
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org