Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: domain of fmeschbe@adobe.com designates
 64.18.1.189 as permitted sender)
From: Felix Meschberger <fmeschbe@adobe.com>
To: "oak-dev@jackrabbit.apache.org" <oak-dev@jackrabbit.apache.org>
Date: Tue, 18 Jun 2013 09:01:41 +0100
Subject: Re: Move MongoMK to Oak Core
Thread-Topic: Move MongoMK to Oak Core
Thread-Index: Ac5r+hL821OoH3aoQUCa/PzRvbJ85g==
Message-ID: <A409B33B-B19D-433B-BF42-7E5F1D017AC4@adobe.com>
References: 
 <CAHCW-mmvUx9a39rOW5eK4i-mOzPiqJx8Yhm9aGAvtrgcYBVEfQ@mail.gmail.com>
In-Reply-To: 
 <CAHCW-mmvUx9a39rOW5eK4i-mOzPiqJx8Yhm9aGAvtrgcYBVEfQ@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi

I have the impression, that this imght solve your short-term issue but in t=
he long term you actually dilute modularity in that you integrte a single, =
special MK implementation into Oak Core.

I may be way off the current implementation, but from a modularization POV =
this sounds perfectly wrong.

Regards
Felix

Am 18.06.2013 um 07:31 schrieb Chetan Mehrotra:

> I wanted to make use of the new Whiteboard support [1] for publishing
> Cache related MBeans and for Scheduler Service. I see two options
>=20
> 1. Move the Whiteboard support to oak Commons
> 2. Move MongoMk to Oak Core
>=20
> Similar requirement was felt for use of StringCache in MongoMK [2].
> There also it was suggested to move Mongo MK to Oak Core. So should we
> move the codebase to Oak Core and change the package from
> o.a.j.mongomk to o.a.j.oak.plugins.mongomk
>=20
> Chetan Mehrotra
>=20
> [1] https://issues.apache.org/jira/browse/OAK-867
> [2] https://issues.apache.org/jira/browse/OAK-861