Return-Path: Delivered-To: apmail-cxf-dev-archive@www.apache.org Received: (qmail 2203 invoked from network); 10 Apr 2009 12:21:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Apr 2009 12:21:12 -0000 Received: (qmail 65094 invoked by uid 500); 10 Apr 2009 12:21:11 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 65012 invoked by uid 500); 10 Apr 2009 12:21:11 -0000 Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list dev@cxf.apache.org Received: (qmail 65002 invoked by uid 99); 10 Apr 2009 12:21:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Apr 2009 12:21:11 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of eoglynn@gmail.com designates 209.85.220.179 as permitted sender) Received: from [209.85.220.179] (HELO mail-fx0-f179.google.com) (209.85.220.179) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Apr 2009 12:21:03 +0000 Received: by fxm27 with SMTP id 27so1305585fxm.30 for ; Fri, 10 Apr 2009 05:20:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=DfiEdexrY53/lOzgM1R2eYcBVsztbY6PCjJT++lmhJ8=; b=QiiLwtCdEfLy1LwGZeR1JJd0pEt+FWxauEbhy1Iwn4WwbwA2rtiDG2EY2/RIJL6EFh MiCP4C1LMyiwPd7gYPKX+O0EFHHDBQjG00ANDXFwBjRIm/jH4NkNtjCkf470XrVDzAMO PrfjLnR7y4YH4uDrnPxJneGKnwXZzakT1DYWE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=cuqT1pDaRo7uYQYt1yZUvYU4rZZkrZJtFCUo8FrqwG2eVAc/uhZSPOKbK1+iauOAtl p1Id3AOVAqu5HhPYrbfo17hxKPXOScKKnFQ4YMwEBbXS7m1iN6sEA28KUrlxu/vpJK2g 8Mj31a2PnDgb/g80TEvUlmRoCeX4B2YjA6efc= MIME-Version: 1.0 Received: by 10.239.133.77 with SMTP id 13mr104691hbu.67.1239366043366; Fri, 10 Apr 2009 05:20:43 -0700 (PDT) In-Reply-To: References: Date: Fri, 10 Apr 2009 13:20:43 +0100 Message-ID: Subject: Re: Distributed OSGi Discovery implementation in CXF From: Eoghan Glynn To: dev@cxf.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi David, This would be a very welcome addition to the distributed OSGi support in CXF! So please, fire away and commit what you've done so far. Thanks, Eoghan 2009/4/10 David Bosschaert : > Hi all, > > Over the past while I have done some experimentation around a possible > implementation of the Distributed OSGi RFC 119 Discovery service. > > The current CXF-DOSGi codebase only contains the Distribution Software > (DSW) component, which means that you need to configure the location > of your remote services manually. Adding a Discovery service (as > specified in RFC 119) would enable dynamic discovery of remote > services as well. > > I've started using Apache Zookeeper as the underlying technology to > implement a Discovery service and at this stage I have it working, > although what I have is not completely finished. > > I think this could be a useful addition to the CXF DOSGi codebase, as > together with the DSW code that's already there it would provide the > implementation of the two core parts of RFC 119. > If folks agree that this is useful to have, I can start contributing > this to the http://svn.apache.org/repos/asf/cxf/dosgi/trunk/discovery > and continue working on it from that location. > > Thoughts anyone? > > Cheers, > > David >