jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chetan Mehrotra <chetan.mehro...@gmail.com>
Subject Re: svn commit: r1577449 - in /jackrabbit/oak/trunk/oak-core/src: main/java/org/apache/jackrabbit/oak/plugins/segment/ main/java/org/apache/jackrabbit/oak/plugins/segment/file/ main/java/org/apache/jackrabbit/oak/plugins/segment/http/ main/java/org/apa...
Date Wed, 02 Apr 2014 11:08:52 GMT
> @Chetan: why would the configs not be stored in the repo? I do not see how this relates
to non-OSGi environments

Well thats the basic config required to configure
DocumentNodeStore/SegmentNodeStore. These config cannot be stored as
content.

Other settings like security related config currently is not read from
NodeStore and in OSGi env is being provided by OSGi ConfigAdmin.

And more other settings like Index are currently stored as content
Chetan Mehrotra


On Wed, Apr 2, 2014 at 3:49 PM, Michael Marth <mmarth@adobe.com> wrote:
>
> On 02 Apr 2014, at 08:06, Jukka Zitting <Jukka.Zitting@gmail.com<mailto:Jukka.Zitting@gmail.com>>
wrote:
>
> That design gets broken if components
> start storing data separately in the repository folder.
>
> Agree with that design principle, but the (shared) file system DS is a valid exception
IMO (same for the S3 DS).
>
> Later we would probably store the config files when using Oak outside
> of std OSGi env like with PojoSR
>
> @Chetan: why would the configs not be stored in the repo? I do not see how this relates
to non-OSGi environments

Mime
View raw message