[jira] [Commented] (OAK-5656) InitialContent depends on document.bundlor.BundlingConfigInitializer

["Chetan Mehrotra (JIRA)" <ji...@apache.org>]

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

Chetan Mehrotra commented on OAK-5656:
--------------------------------------

[~anchela] RepositoryInitializer based approach was discussed as part of OAK-4975 and also on the [oak-dev|https://lists.apache.org/thread.html/6f19a1390f5c3161311815378eef7688607329ae63d891bf04a4dc62@%3Coak-dev.jackrabbit.apache.org%3E] and consensus then was to keep this simple and bootstrap this config from within InitialContent

> InitialContent depends on document.bundlor.BundlingConfigInitializer
> --------------------------------------------------------------------
>
>                 Key: OAK-5656
>                 URL: https://issues.apache.org/jira/browse/OAK-5656
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>            Reporter: angela
>              Labels: tech-debt
>             Fix For: 1.8
>
>
> [~chetanm], in the light of OAK-4975 a dependency to the document nodestore code got introduced in {{org.apache.jackrabbit.oak.plugins.nodetype.write.InitialContent}} by adding the following line:
> {code}
>         BundlingConfigInitializer.INSTANCE.initialize(builder);
> {code}
> the {{BundlingConfigInitializer}} is defined in the {{org.apache.jackrabbit.oak.plugins.document.bundlor}}.
> To me that looks quite troublesome and I don't think the generic JCR-InitialContent should have any dependency on the document nodestore code base.
> Why not defining a dedicated {{RepositoryInitializer}} for that kind of init an making sure it is listed in the (default) setup scenarios (or at least in those that actually have a document store and thus require this)?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)