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] Resolved: (FELIX-578) ComponentFactoryImpl.newInstance() must create the component synchronously
Date Fri, 30 May 2008 19:32:45 GMT

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

Felix Meschberger resolved FELIX-578.

       Resolution: Fixed
    Fix Version/s: scr-1.0.1

Fixed in Rev. 661830: ComponentFactoryImpl.newInstance() now ensures the component is enabled
synchronously, that is the ComponentInstance returned will provide the actual component instance
in its getInstance() method.

Please close this bug, if it fixes your issue. Thanks.

> ComponentFactoryImpl.newInstance() must create the component synchronously
> --------------------------------------------------------------------------
>                 Key: FELIX-578
>                 URL: https://issues.apache.org/jira/browse/FELIX-578
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR)
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: scr-1.0.1
> The ComponentFactoryImpl.newInstance() method internally calls the AbstractComponentManager.enable()
method to enable and activate the newly created component instance. The enable() method in
turn schedules the enableInternal() method to run asynchronously.
> In the context of the ComponentFactoryImpl.newInstance() method this asynchronous enablement
is not correct, as the caller expects the ComponentInstance returned from the newInstance
to be active.
> Hence the ComponentFactoryImpl.newInstance() method must be able to enable the created
component synchronously.

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

View raw message