[
https://java.net/jira/browse/GLAZEDLISTS-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
brands updated GLAZEDLISTS-596:
-------------------------------
Summary: Provide GlazedLists#syncEventListToEventList to sync two EventLists (was: Provide GlazedLists#syncEventListToEventList to sync to EventLists)
> Provide GlazedLists#syncEventListToEventList to sync two EventLists
> -------------------------------------------------------------------
>
> Key: GLAZEDLISTS-596
> URL:
https://java.net/jira/browse/GLAZEDLISTS-596> Project: glazedlists
> Issue Type: Improvement
> Components: core
> Reporter: brands
> Assignee: brands
> Fix For: 1.10.0
>
>
> GlazedLists#syncEventListToEventList will sync two Event Lists with appropriate locking applied, e.g. when modifying the target list a write lock is aquired first.
> This feature is useful for syncing event lists in different list pipelines that share no common lock and publisher.
> GlazedLists#syncEventListToEventList complements
> GlazedLists#syncEventListToList where a normal list is the sync target. But this method should not be used for syncing to an EventList because it obviously misses correct locking of the target event list.
> The return value of both sync-methods where changed to return the concrete ListEventListener implementation as they now offer a dispose-method to stop the syncing.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)