felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-1666) Missing support for DS 1.1 specified lazy activation behavior
Date Tue, 13 Oct 2009 15:19:31 GMT

    [ https://issues.apache.org/jira/browse/FELIX-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765115#action_12765115

Felix Meschberger commented on FELIX-1666:

Thanks for digging in and providing the patch. I try to apply it tonight.

> Enabled, satisfied components should have their provided services registered as a ServiceFactory

Are you sure ? I think the components providing a service should only be registered as ServiceFactory
iff they are defined as delayed or as service factories in the descriptor. Service components
declared as "immediate=true" should IMHO registered as plain services and thus should cause
the bundle to be really started.


> Missing support for DS 1.1 specified lazy activation behavior
> -------------------------------------------------------------
>                 Key: FELIX-1666
>                 URL: https://issues.apache.org/jira/browse/FELIX-1666
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR)
>    Affects Versions: scr-1.0.8
>            Reporter: Matthew Sykes
>             Fix For: scr-1.2.0
>         Attachments: lazy-bundle-state.diff
> While attempting to move code from the Equinox implementation of DS to the Felix implementation,
I discovered that the Felix SCR does not seem to support processing and activation of component
configurations that are declared in bundles awaiting lazy activation.  The DS 1.1 specification,
section 112.8.2 indicates that bundles awaiting lazy activation are to be processed when the
SCR starts (and, presumedly by extension, as bundles bundles are starting/started).
> It appears that Felix has implemented most of the DS 1.1 support already so it appears
this is an oversight.

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

View raw message