You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Marcel Offermans (JIRA)" <ji...@apache.org> on 2010/02/15 11:15:27 UTC
[jira] Created: (FELIX-2078) Not all callbacks invoked when
declaring a service as required and starting it after dependencies
Not all callbacks invoked when declaring a service as required and starting it after dependencies
-------------------------------------------------------------------------------------------------
Key: FELIX-2078
URL: https://issues.apache.org/jira/browse/FELIX-2078
Project: Felix
Issue Type: Bug
Components: Dependency Manager
Reporter: Marcel Offermans
Assignee: Marcel Offermans
When you first register 2 services and then create a service that depends on them, marking the dependency as required causes one of the two callbacks to fail.
Workaround is to declare the dependency as optional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-2078) Not all callbacks invoked when
declaring a service as required and starting it after dependencies
Posted by "Marcel Offermans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Offermans resolved FELIX-2078.
-------------------------------------
Resolution: Fixed
The committed fix solves the issue. The test for this fix confirms that.
> Not all callbacks invoked when declaring a service as required and starting it after dependencies
> -------------------------------------------------------------------------------------------------
>
> Key: FELIX-2078
> URL: https://issues.apache.org/jira/browse/FELIX-2078
> Project: Felix
> Issue Type: Bug
> Components: Dependency Manager
> Reporter: Marcel Offermans
> Assignee: Marcel Offermans
>
> When you first register 2 services and then create a service that depends on them, marking the dependency as required causes one of the two callbacks to fail.
> Workaround is to declare the dependency as optional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.