cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (DOSGI-27) Discovery problem when two dependent bundles export interfaces
Date Fri, 24 May 2013 14:34:26 GMT

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

Christian Schneider closed DOSGI-27.
------------------------------------

    
> Discovery problem when two dependent bundles export interfaces
> --------------------------------------------------------------
>
>                 Key: DOSGI-27
>                 URL: https://issues.apache.org/jira/browse/DOSGI-27
>             Project: CXF Distributed OSGi
>          Issue Type: Bug
>         Environment: felix-2.0.1
>            Reporter: Alexander Broekhuis
>            Assignee: David Bosschaert
>             Fix For: 1.2
>
>         Attachments: cxf-dosgi-ri-multibundle-distribution-1.2-SNAPSHOT.tar.gz, cxf-dosgi-ri-singlebundle-distribution-1.2-SNAPSHOT.jar,
testcase.tar.gz
>
>
> I have the following setup:
> - first bundle with a common interface (common)
> - second bundle with a common interface (commonb)
> - client bundle with a service implementing the first common interface (client)
> - server bundle with a service implementing the second common interface (server)
> Both the client and the server export the implemented interface.
> The client service has a tracker to the interface published by the server.
> So the interface of the client isn't used.
> Further, I use the 1.1 singlebundle distribution.
> If I run this situation, the client most of the time does not track any server interface.
Stopping the client and the distributed osgi bundle, and then first starting the dosgi bundle,
and after that the client, makes the tracker work.
> If I remove the remote properties from the client the tracker works. I can start stop
any way I want, it keeps finding the server interface.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message