Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Date: Thu, 15 Mar 2012 15:31:42 +0000 (UTC)
From: =?utf-8?Q?Michael_D=C3=BCrig_=28Created=29_=28JIRA=29?=
 <jira@apache.org>
To: oak-dev@jackrabbit.apache.org
Message-ID: 
 <1806253471.19363.1331825502278.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (OAK-17) Modularisation and configuration concept
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Modularisation and configuration concept
----------------------------------------

                 Key: OAK-17
                 URL: https://issues.apache.org/jira/browse/OAK-17
             Project: Jackrabbit Oak
          Issue Type: Task
          Components: core, jcr
            Reporter: Michael D=C3=BCrig


We need to come up with a concept for modularisation and configuration. The=
re is some initial discussion on the list [1]. While we need to make sure t=
hat we are interoperable with OSGi, I don't think we should use OSGi itself=
 for the lower granular pieces. That is, for certain subsystems of oak-jcr =
or oak-core for example. Still we need a way for handling dependencies betw=
een and configuration of implementation classes. In the case of oak-jcr the=
re is the GlobalContext class. This is basically poor man's dependency inje=
ction and I'd like to get rid of it as soon as we have a better solution. W=
hat I'd like to have on that level is compile time dependency injection suc=
h that we get loose coupling between implementation classes but don't get t=
he additional complexity from run time dependency injection (aka OSGi).

[1] http://markmail.org/thread/hpssa4r6brlt5cwa

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira