cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Bosschaert (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CXF-2578) Discovery problem when two dependent bundles export interfaces
Date Fri, 11 Dec 2009 14:12:18 GMT

    [ https://issues.apache.org/jira/browse/CXF-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789320#action_12789320
] 

David Bosschaert commented on CXF-2578:
---------------------------------------

Hi Alexander, 
I've finally been able to reproduce this. It definitely has something to do with bundle ordering.
It doesn't always show up if the bundle ordering at startup happens to be beneficial. In fact
I had never seen it on Windows as the default seems to work there. However when I looked at
it with Equinox on Linux the default ordering exposed the problem there.
I will look into fixing this.

In the mean time you can work around this by giving your client bundle a higher start level
than the rest. That consistently gives the correct result for me.

> Discovery problem when two dependent bundles export interfaces
> --------------------------------------------------------------
>
>                 Key: CXF-2578
>                 URL: https://issues.apache.org/jira/browse/CXF-2578
>             Project: CXF
>          Issue Type: Bug
>          Components: Distributed-OSGi
>    Affects Versions: dOSGi-1.1
>         Environment: felix-2.0.1
>            Reporter: Alexander Broekhuis
>            Assignee: David Bosschaert
>         Attachments: 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message