[
https://issues.apache.org/jira/browse/CXF-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Bosschaert updated CXF-2578:
----------------------------------
Attachment: cxf-dosgi-ri-multibundle-distribution-1.2-SNAPSHOT.tar.gz
Great, thanks for testing this out.
I was able to reproduce your issue with the 1.1 release, but the fix to the
discovery activator that I put in at
http://svn.apache.org/repos/asf/cxf/dosgi/trunk/discovery/distributed/cxf-discovery/src/main/java/org/apache/cxf/dosgi/discovery/zookeeper/Activator.java
revision 888782 consistently fixed this issue for me too.
So the single bundle distro that I attached was actually just trunk that I
built (with that fix). I've attached the multi bundle distro from the same
build as requested.
Hopefully this will keep you going for the time being. As mentioned before
we're working on refactoring the implementation to be compliant with the Remote
Service Admin spec at the moment. Although that work should keep things
backward compatible from a user's point of view, the actual implementation
details will change
> 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:
> 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.
-
You can reply to this email to add a comment to the issue online.
