[
https://issues.apache.org/jira/browse/JCR-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1753:
-------------------------------
Affects Version/s: (was: core 1.4.5)
Fix Version/s: 1.5
Assignee: Jukka Zitting
Summary: Allow means force a Repository to synchronize with the
cluster (was: Allow means force a Repository to synchronize with the data
store)
Hmm, there's a somewhat releated long discussion ([1] and [2]) about
JackrabbitRepository.shutdown() that we had earlier this year. This method is
not nearly as intrusive as the shutdown() method, but there might be valid
reasons why it shouldn't be exposed to just any client.
[1] http://markmail.org/message/fqyypq5x6bma4ike
[2] http://markmail.org/message/dsqyv3rafo4j5xea
> Allow means force a Repository to synchronize with the cluster
> --------------------------------------------------------------
>
> Key: JCR-1753
> URL: https://issues.apache.org/jira/browse/JCR-1753
> Project: Jackrabbit
> Issue Type: New Feature
> Components: clustering, jackrabbit-api, jackrabbit-core
> Reporter: Micah Whitacre
> Assignee: Jukka Zitting
> Fix For: 1.5
>
> Attachments: 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.
