mirror of
https://github.com/Alfresco/alfresco-community-repo.git
synced 2025-08-07 17:49:17 +00:00
Merged V3.2 to HEAD
17462: ETHREEOH-3346: New meaning to synchronization.synchronizeChangesOnly property - In the LDAP sync performance optimizations we always used the differential queries to determine the users and groups to be updated. Deletions were determined by a separate query. - This meant that if you ever did want to force the update of all users it wasn't possible. - So now when the flag is false it means don't use differential queries in the scheduled sync job. - The scheduled job now processes deletions regardless. - The default value for the property is now true. 17431: ETHREEOH-3274: Refix NTLM support for share - Fixed NPE introduced by ETHREEOH-2767 - Made web.xml validate against schema for JBoss - Reintroduced missing open comment in webscript-framework-config-custom.xml.sample 17426: ETHREEOH-2997: Fix ticket parameter passing into NTLM/Kerberos WebDAV authentication filters - A NPE was stopping it from working 17425: ETHREEOH-3282: Fixed NPE preventing upload from working with NTLM SSO enabled 17368: ETHREEOH-3197: Use utf8_bin collation in MySQL out of the box to avoid problems with comparison of accented characters 17361: ETHREEOH-3276: Don't attempt to start an LDAP sync when the repository is read only 17347: ETHREEOH-3206: Fix LocalFeedTaskProcessor to work with JBoss 5 git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@17464 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
This commit is contained in:
@@ -48,19 +48,21 @@ public interface UserRegistrySynchronizer
|
||||
* users and groups last retrieved from the same sources. Any updates and additions made to those users and groups
|
||||
* are applied to the local Alfresco copies.
|
||||
*
|
||||
* @param force
|
||||
* Should a complete or partial set of information be queried from the external sources? When
|
||||
* <code>true</code> then <i>all</i> users and groups are queried. With this complete set of information,
|
||||
* the implementation is able to identify which users and groups have been deleted, so it will delete
|
||||
* users and groups as well as update and create them. When <code>false</code> then each source is only
|
||||
* queried for those users and groups modified since the most recent modification date of all the objects
|
||||
* last queried from that same source. In this mode, local users and groups are created and updated, but
|
||||
* not deleted.
|
||||
* @param forceUpdate
|
||||
* Should the complete set of users and groups be updated / created locally or just those known to have
|
||||
* changed since the last sync? When <code>true</code> then <i>all</i> users and groups are queried from
|
||||
* the user registry and updated locally. When <code>false</code> then each source is only queried for
|
||||
* those users and groups modified since the most recent modification date of all the objects last
|
||||
* queried from that same source.
|
||||
* @param allowDeletions
|
||||
* Should a complete set of user and group IDs be queried from the user registries in order to determine
|
||||
* deletions? This parameter is independent of <code>force</code> as a separate query is run to process
|
||||
* updates.
|
||||
* @param splitTxns
|
||||
* Can the modifications to Alfresco be split across multiple transactions for maximum performance? If
|
||||
* <code>true</code>, users and groups are created/updated in batches of 10 for increased performance. If
|
||||
* <code>false</code>, all users and groups are processed in the current transaction. This is required if
|
||||
* calling synchronously (e.g. in response to an authentication event in the same transaction).
|
||||
*/
|
||||
public void synchronize(boolean force, boolean splitTxns);
|
||||
public void synchronize(boolean forceUpdate, boolean allowDeletions, boolean splitTxns);
|
||||
}
|
Reference in New Issue
Block a user