topic Re: deletePermissions throws ConstraintViolationException in Alfresco Archive

deletePermissions throws ConstraintViolationException

dgildeh — Wed, 03 Nov 2010 11:01:17 GMT

On Alfresco Community v3.2.0 (r2 2440) schema 3,300 I have written a patch that does the essentially executes the following code to loop through a set of nodes, remove their current permissions and apply new ones:for (NodeRef node : nodes) { // Delete all the permissions on th

Re: deletePermissions throws ConstraintViolationException

gyro_gearless — Wed, 03 Nov 2010 14:42:53 GMT

I suppose deletePermissions() is broken in 3.2, see for example http://issues.alfresco.com/jira/browse/ALF-4837

For one of my webscripts, i use this as workaround:


                    //
                    // The obvious way - it just doesn't work (see http://issues.alfresco.com/jira/browse/ALF-4837)
                    //
                    // this.permissionService.deletePermissions(targetPathRef);
                    
                    Set<AccessPermission> setPermissions = this.permissionService.getAllSetPermissions(targetPathRef);
                    for (AccessPermission p : setPermissions)
                    {
                        if (p.isSetDirectly())
                        {
                            String authority = p.getAuthority();
                            String permission = p.getPermission();
                            
                            if (smLogger.isDebugEnabled())
                            {
                                smLogger.debug("- " + authority + ":" + permission);
                            }
                            this.permissionService.deletePermission(targetPathRef, authority, permission);
                        }
                    }
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Re: deletePermissions throws ConstraintViolationException

dgildeh — Wed, 03 Nov 2010 15:42:25 GMT

Thanks Andreas - I tried a similar solution likes yours and worked around the issue. I noticed the issue you pointed to is still not resolved in 3.4 so hope they put a fix for this soon, was worried my database was corrupted!