You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2017/02/14 15:30:42 UTC
[jira] [Created] (OAK-5656) InitialContent depends on
document.bundlor.BundlingConfigInitializer
angela created OAK-5656:
---------------------------
Summary: 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
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)