By the way, the doc for the dm shell can be found here: http://felix.apache.org/documentation/subprojects/apache-felix-dependency-manager/tutorials/leveraging-the-shell.html
cheers /Pierre On Sat, Sep 10, 2016 at 12:10 AM, Pierre De Rop <[email protected]> wrote: > Hi Mdu, > > indeed, it might be possible that the service consumer bundle is importing > the package of the service it consumes from a bundle b1, while the service > provider bundle is importing the package of the service from another bundle > b2. in this case, the consumer won't see the service. > > can you please provide the following: > > 1) the package name of the service the consumer is depending on; > > 2) from web console, go to OSGi -> Bundles, then click on the service > provider bundle, and indicate what is displayed for the "Imported Packages" > section. > > 3) do the same for the service consumer bundle. > > then we'll see if both service provider bundle and service consumer bundle > are importing the service package from the same place. > > now, maybe it could also help to use the dm shell: if not installed, then > install the dm shell bundle; and type "dm <id of the service provider > bundle>", and provide what is displayed. > > then type "dm <id of the service consumer bundle>", and also provide what > is displayed. > > the "dm na" displays all unavailable components, and the "dm wtf" display > root causes which might block the activation of many components (for > example, if A depends on B , and B depends on C, and C is unavailable, then > "dm wtf" will only display "C"). > > you could also, if possible, provide the Activator code for both service > consumer and service provider. > (send it to me by mail, in case you don't want to do that in this mailing > list ... if possible). > > cheers; > /Pierre >
