You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (Jira)" <ji...@apache.org> on 2020/10/08 14:31:00 UTC

[jira] [Assigned] (KARAF-5767) missing OSGi service for @Reference in Action does not lead to failed diag but

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

Jean-Baptiste Onofré reassigned KARAF-5767:
-------------------------------------------

    Assignee:     (was: Jean-Baptiste Onofré)

> missing OSGi service for @Reference in Action does not lead to failed diag but 
> -------------------------------------------------------------------------------
>
>                 Key: KARAF-5767
>                 URL: https://issues.apache.org/jira/browse/KARAF-5767
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf
>    Affects Versions: 4.2.0
>            Reporter: Michael Vorburger
>            Priority: Major
>
> While [migrating a Karaf command from extending deprecated OsgiCommandSupport to implementing the Action interface|https://git.opendaylight.org/gerrit/#/c/72204], I've noticed that if you have a {{@Reference}} to a type under which there is no OSGi Service registered, then that command is simply ignored - without any error in the log.
> While I understand perfectly well that this lazy initialiation is how Declarative Services (DS) work, because the bundle that provides said service could still be installed later, it still seems to me that {{diag}} (which is based on {{org.apache.karaf.bundle.core.BundleService}} AFAIK) could and in an ideal world should report such missing services.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)