[jira] Updated: (SLING-408) Repository service not registered when using Equinox Declarative Services

["Felix Meschberger (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger updated SLING-408:
------------------------------------

    Affects Version/s: JCR Jackrabbit Server 2.0.4
                       JCR Jackrabbit Client 2.0.2
                       JCR API 2.0.2
        Fix Version/s:  JCR Jackrabbit Client 2.0.4

> Repository service not registered when using Equinox Declarative Services
> -------------------------------------------------------------------------
>
>                 Key: SLING-408
>                 URL: https://issues.apache.org/jira/browse/SLING-408
>             Project: Sling
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: JCR Jackrabbit Server 2.0.4, JCR Jackrabbit Client 2.0.2, JCR API 2.0.2
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: JCR Jackrabbit Server 2.0.6,  JCR Jackrabbit Client 2.0.4
>
>
> While trying to run the jcr/jackrabbit-server bundle inside Equinox with the Equinox Declarative Services and Configuration Admin implementations, I discovered, that the handling of ComponentFactories is different in the Equinox DS and Apache Felix DS:
>    * Equinox DS seems to expect factory components to be set as immediate="false", while Felix DS expects immediate="true"
>    * Equinox DS does not seem to start the services properly
> I am not sure, whether this is actually related to wrong implementation in Felix DS or a bug in Equinox DS. This will have to be investigated.
> Versions used:
>   Equinox DS: org.eclipse.equinox.ds_1.0.0.v20070226.jar
>   Felix DS: 1.0.0

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.