[GitHub] [jackrabbit-oak] enapps-enorman edited a comment on pull request #471: OAK-9675 allow authorizable properties defined by a mixin

[GitBox <gi...@apache.org>]

enapps-enorman edited a comment on pull request #471:
URL: https://github.com/apache/jackrabbit-oak/pull/471#issuecomment-1028296674


   @anchela The mixin handling proposed here should not have any impact at all on any state stored under a subtree of the user/group node.  If you look at AuthorizablePropertiesImpl line 242 it is checking if the path equals the user/group home path before doing any of the new mixin checking and handing.  So all of the behavior for those subtree scenarios is the same as it was before.  I believe that the subtree handling has always included all the properties that exist there regardless of the mixin types or primary type of the subtree nodes.  If I am not mistaken, the properties stored on the main home folder was always the only one that was checking where the property definition came from.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@jackrabbit.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org