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 "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2018/07/18 07:14:00 UTC
[jira] [Resolved] (OAK-7570) [DirectBinaryAccess][DISCUSS] How to
access HttpBlobProvider from oak-jcr
[ https://issues.apache.org/jira/browse/OAK-7570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger resolved OAK-7570.
-----------------------------------
Resolution: Resolved
I'm resolving this issue because the consensus is to register the HttpBlobProvider with the Whiteboard and then use it in oak-jcr.
> [DirectBinaryAccess][DISCUSS] How to access HttpBlobProvider from oak-jcr
> -------------------------------------------------------------------------
>
> Key: OAK-7570
> URL: https://issues.apache.org/jira/browse/OAK-7570
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: jcr
> Reporter: Matt Ryan
> Assignee: Matt Ryan
> Priority: Major
>
> Open discussion related to OAK-7569:
> The [original pull request|https://github.com/apache/jackrabbit-oak/pull/88] proposes changes to oak-api, oak-segment-tar, oak-store-document, oak-core, and oak-jcr as well as oak-blob-plugins, oak-blob-cloud, and oak-blob-azure. Would it be possible / better to keep the changes local to the oak-blob-* bundles and avoid making changes throughout the stack?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)