[
https://issues.apache.org/jira/browse/SLING-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommaso Teofili resolved SLING-4062.
------------------------------------
Resolution: Fixed
> Sling replication deleting ACLs nodes
> -------------------------------------
>
> Key: SLING-4062
> URL: https://issues.apache.org/jira/browse/SLING-4062
> Project: Sling
> Issue Type: Bug
> Components: Replication
> Reporter: Laurie byrum
> Assignee: Tommaso Teofili
>
> I use
> @Reference(target = "(name=blah-reverse)", policy =
> ReferencePolicy.DYNAMIC,
> cardinality = ReferenceCardinality.OPTIONAL_UNARY)
> ReplicationAgent replicationAgent;
> public createUser() {
> final UserManager userManager = AccessControlUtil.getUserManager(session);
> User user = (User)userManager.getAuthorizable(userId);
> if (user == null) {
> user = userManager.createUser(userId, password, new
> Principal() {
> @Override
> public String getName() {
> return userId;
> }
> }, userPath);
> session.save();
> }
> }
> ...
> private void reverseReplicate(String path) throws
> AgentReplicationException {
> if (replicationAgent != null) {
> ReplicationRequest replicationRequest = new ReplicationRequest(0,
> ReplicationActionType.ADD, path);
> replicationAgent.execute(replicationRequest);
> }
> }
> If you look at the user node before replication happens, there is a
> rep:policy node under it with jcr:all access for the user. After the reverse
> replication poll interval happens and replication completes, the rep:policy
> node is missing!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
