You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2009/12/04 10:59:20 UTC

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

    [ https://issues.apache.org/jira/browse/SLING-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785845#action_12785845 ] 

Felix Meschberger commented on SLING-408:
-----------------------------------------

The second issue has in fact been another wrong implementation in the Felix DS implementation (see FELIX-1416). 

> 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
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>
> 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.