Discovery problem when two dependent bundles export interfaces

[Alexander Broekhuis <a....@gmail.com>]

Hi all,

I have the following setup:
- first bundle with a common interface
- second bundle with a common interface
- client bundle with a service implementing the first common interface
- server bundle with a service implementing the second common interface

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.

Is there something wrong with this structure?



-- 
Met vriendelijke groet,

Alexander Broekhuis

Re: Discovery problem when two dependent bundles export interfaces

[David Bosschaert <da...@gmail.com>]

Hi Alexander,

On the face of it this should work just fine.
Could you please file a JIRA for this issue and attach a small
testcase to reproduce your problem?

https://issues.apache.org/jira/secure/CreateIssue!default.jspa

Thanks,

David

2009/12/9 Alexander Broekhuis <a....@gmail.com>:
> Hi all,
>
> I have the following setup:
> - first bundle with a common interface
> - second bundle with a common interface
> - client bundle with a service implementing the first common interface
> - server bundle with a service implementing the second common interface
>
> 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.
>
> Is there something wrong with this structure?
>
>
>
> --
> Met vriendelijke groet,
>
> Alexander Broekhuis
>