[ 
https://issues.apache.org/jira/browse/OAK-7510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16495256#comment-16495256
 ] 

angela edited comment on OAK-7510 at 5/31/18 10:11 AM:
-------------------------------------------------------

[~stillalex], -just looked at the usage of {{OpenAuthorizationConfiguration}}. 
Shouldn't adding the {{PrivilegeConfigurationImpl}} to the 
{{OpenSecurityProvider}} do the trick already for most of the cases? - 
just wanted to try it out and obviously this won't work due to the module 
boundary... but why is the implementation specific privilege representation in 
the repo mandatory? (asking myself). So, either it's built-in hardwired and 
mandatory or it's at least in theory pluggable and then it must not be 
mandatory.


was (Author: anchela):
[~stillalex], just looked at the usage of {{OpenAuthorizationConfiguration}}. 
Shouldn't adding the {{PrivilegeConfigurationImpl}} to the 
{{OpenSecurityProvider}} do the trick already for most of the cases? 

> Run repository initializers with hooks
> --------------------------------------
>
>                 Key: OAK-7510
>                 URL: https://issues.apache.org/jira/browse/OAK-7510
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Alex Deparvu
>            Assignee: Alex Deparvu
>            Priority: Major
>              Labels: modularization
>
> Currently the repository initializers (RepositoryInitializer and 
> WorkspaceInitializer) run when the repo boots without any hooks [0] which 
> means that current RepositoryInitializers need to setup custom Roots (roots 
> with hardcoded editor providers like NamespaceEditorProvider and 
> TypeEditorProvider) on top of the provided builders to be able to setup 
> properly. I'm looking at the InitialContent [1] and the CugConfiguration [2] 
> in the context of installing node types.
> I would like to look into removing the hardcoded providers and trying to run 
> all existing editors over the content produced by the initializers.
> As an added benefit this will allow decoupling of hard dependencies between 
> components (see for example OAK-7499)
> [0] 
> https://github.com/apache/jackrabbit-oak/blob/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/Oak.java#L687
>  
> [1] 
> https://github.com/apache/jackrabbit-oak/blob/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/InitialContent.java#L134
> [2] 
> https://github.com/apache/jackrabbit-oak/blob/trunk/oak-authorization-cug/src/main/java/org/apache/jackrabbit/oak/spi/security/authorization/cug/impl/CugConfiguration.java#L162



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to