Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Message-ID: <880964687.1260475098088.JavaMail.jira@brutus>
Date: Thu, 10 Dec 2009 19:58:18 +0000 (UTC)
From: "Alexander Broekhuis (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Subject: [jira] Commented: (CXF-2578) Discovery problem when two dependent
 bundles export interfaces
In-Reply-To: <474275124.1260371358180.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alexander Broekhuis commented on CXF-2578:
------------------------------------------

Yes,

With the 1.1 snapshot version the tracker always sees the service being added. With the 1.1 release it doesn't.

> 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.