You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Mdu (JIRA)" <ji...@apache.org> on 2016/09/26 18:12:20 UTC

[jira] [Created] (FELIX-5365) Generate warning on service published and consumed on same interface but different bundles

Mdu created FELIX-5365:
--------------------------

             Summary: Generate warning on service published and consumed on same interface but different bundles
                 Key: FELIX-5365
                 URL: https://issues.apache.org/jira/browse/FELIX-5365
             Project: Felix
          Issue Type: Improvement
          Components: Dependency Manager Shell
    Affects Versions: org.apache.felix.dependencymanager-r8
         Environment: Eclipse Mars/Bndtools 3.x
            Reporter: Mdu
            Priority: Critical
             Fix For: org.apache.felix.dependencymanager-r9


Scenario:
1. Service S1 is published on interface from package a.b.c exported by bundle B1.

2. Component C1 requests (depends on required=true) S1 using an interface from package a.b.c exported by bundle B2 (or its own bundle).

3. Component C1 stays unresolved due to missing S1 even though S1 is successfully registered and available.

Root Cause:
Services are considered different if an interface they export is from 2+ different bundles.

Feature Improvement Request:
It'd be a time-saver for troubleshooting purposes for "dm wtf" command to warn of this subtle mismatch. 

A warning could be: 

Component C1 is waiting for a dependency on interface 'a.b.c' published under package a.b.c exported by bundle B2. There exist a potentially matching service published under interface of the same name but exported by bundle B1.  

Also see http://apache-felix.18485.x6.nabble.com/Help-debug-ServiceDependency-in-DM4-R8-td5018369.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)