[
https://issues.apache.org/jira/browse/OAK-6980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16272758#comment-16272758
]
Alex Deparvu commented on OAK-6980:
-----------------------------------
The direction seems good to me. I'm wondering if it would be worth it to have a
consistent way of injecting the 2 providers, right now some of the classes have
setters, some constructors with the new fields. Could we go for a single
approach (setters) across the board?
> Replacement for RootFactory and TreeFactory
> -------------------------------------------
>
> Key: OAK-6980
> URL: https://issues.apache.org/jira/browse/OAK-6980
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: auth-external, authorization-cug, core, security-spi
> Reporter: angela
> Assignee: angela
> Fix For: 1.8
>
>
> in the light of the m12n effort we had to rip apart the _plugins/tree_
> package and leave 2 utilities ({{RootFactory}} and {{TreeFactory}} in
> _oak-core_ due to tight coupling with implementation details.
> i would like provide a replacement for custom security modules that are
> likely to make use of these factories and should not need to define a
> dependency to _oak-core_. Any proposal we come up with can be tested/verified
> with _oak-auth-external_ and _oak-authorization-cug_.
> cc: [~stillalex]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
