Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Thu, 13 Sep 2012 01:05:07 +1100 (NCT)
From: "Chetan Mehrotra (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: <671321698.69477.1347458707941.JavaMail.jiratomcat@arcas>
In-Reply-To: <98962676.43737.1346928908237.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (JCR-3420) Improving Jackrabbit integration
 within OSGi and other managed environment
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/JCR-3420?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D134540=
15#comment-13454015 ]=20

Chetan Mehrotra commented on JCR-3420:
--------------------------------------

ya thinking more about it we can get rid of extra attribute. So the logic w=
ould be

1. Check for all the classNames as part of BeanConfigVisitor.=20
  a) If the class object corresponding to that className is an interface th=
en corresponding instance for that bean MUST be obtained via factory.=20
  b) If the class object is not an interface then no DI would be done and b=
ean instance would be directly instantiated as per current logic.=20
2. Once all such dependencies are determined use that to control when the r=
epository should be started
3. When newInstance call is done look for a service from managing container=
 (like Service Registry in OSGi) which implements that interface and use th=
at. If no such service is found fail the startup.

In current JR impl all such cases involve interfaces and such an approach s=
hould work fine
               =20
> Improving Jackrabbit integration within OSGi and other managed environmen=
t
> -------------------------------------------------------------------------=
-
>
>                 Key: JCR-3420
>                 URL: https://issues.apache.org/jira/browse/JCR-3420
>             Project: Jackrabbit Content Repository
>          Issue Type: New Feature
>          Components: config, jackrabbit-core
>    Affects Versions: 2.5.1
>            Reporter: Michael D=C3=BCrig
>         Attachments: JCR-3420-osgi-factory.patch
>
>
> While using jackrabbit in managed environment like Sling, Spring etc
> its easy for other components to access the Repository service.
> However its tricky to use managed components of those env within
> Jackrabbit as it creates the instances on its own. To simplify such
> integration it would be helpful if JR exposes a factory service which
> is used to create the various beans from the JR configuration.
> See http://markmail.org/message/johbo2dnepwtjogm for Chetan's initial pro=
posal and POC implementation.=20

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira