[
https://issues.apache.org/jira/browse/JCR-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1753:
-------------------------------
Resolution: Fixed
Fix Version/s: 1.6.0
Status: Resolved (was: Patch Available)
Committed a slightly modified version of the patch in revision 792211. Merged
to the 1.x branch in revision 792212.
Cluster synchronization is now enabled by default for Session.refresh(boolean).
The synch can be selectively disabled per session by setting the
"org.apache.jackrabbit.disableClusterSyncOnRefresh" attribute to any non-null
value. Alternatively a SessionImpl subclass can disable (or enable) this
feature for all refresh() calls by overriding the protected
clusterSyncOnRefresh() method.
> Allow means force a Repository to synchronize with the cluster
> --------------------------------------------------------------
>
> Key: JCR-1753
> URL: https://issues.apache.org/jira/browse/JCR-1753
> Project: Jackrabbit Content Repository
> Issue Type: New Feature
> Components: clustering, jackrabbit-core
> Reporter: Micah Whitacre
> Assignee: Jukka Zitting
> Fix For: 1.6.0
>
> Attachments:
> 0001-JCR-1753-Allow-means-force-a-Repository-to-synchron.patch,
> 0002-JCR-1753-Allow-means-force-a-Repository-to-synchron.patch,
> JCR-1753-sync-in-refresh.patch, JCR-1753.tar.gz
>
>
> Based on the thread on the user mailing list I'm logging this to propose
> adding a sync() method to force cluster synchronization using the
> JackrabbitRepository extension API.
> The purpose of the method is such that in a distributed clustered environment
> sometime cluster synchronization does or has not occurred such that certain
> repositories are in a stale state. This method would provide a means to
> force a repository to update pull in possible changes made by other
> Jackrabbit repositories.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
