Return-Path: X-Original-To: apmail-directory-dev-archive@www.apache.org Delivered-To: apmail-directory-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EE11D7ECA for ; Tue, 20 Sep 2011 12:21:56 +0000 (UTC) Received: (qmail 3453 invoked by uid 500); 20 Sep 2011 12:21:56 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 3401 invoked by uid 500); 20 Sep 2011 12:21:56 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 3393 invoked by uid 99); 20 Sep 2011 12:21:56 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Sep 2011 12:21:56 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of hasnoadditives@gmail.com designates 209.85.161.50 as permitted sender) Received: from [209.85.161.50] (HELO mail-fx0-f50.google.com) (209.85.161.50) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Sep 2011 12:21:47 +0000 Received: by fxh10 with SMTP id 10so518949fxh.37 for ; Tue, 20 Sep 2011 05:21:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=qWiji0mrg9KxJ8facfvxdXeTeCn8VFQwj5Vu5E2pI6Y=; b=RfQW/A0e4zNLKG7kfOgXmDrEZ0L1ngMpDxyCzeH8y8570FICT3zPWw5Tw0O3n8bAOR Vvdj+VSt2mIQumiD+fC9axrTv4Gip/sEf0JFpDX180kPERYZd696/hN2PLN+XUQcgjP9 yWJGxv1f9m7lnlo2Nr5yqc6pBWrCJwN27ZoC0= Received: by 10.223.37.68 with SMTP id w4mr1256555fad.49.1316521287155; Tue, 20 Sep 2011 05:21:27 -0700 (PDT) Received: from [10.0.0.15] (213-33-20-208.adsl.highway.telekom.at. [213.33.20.208]) by mx.google.com with ESMTPS id h16sm1292864fab.19.2011.09.20.05.21.26 (version=SSLv3 cipher=OTHER); Tue, 20 Sep 2011 05:21:26 -0700 (PDT) Message-ID: <4E788546.4080809@gmail.com> Date: Tue, 20 Sep 2011 14:21:26 +0200 From: Christoph Czurda User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.21) Gecko/20110831 Thunderbird/3.1.13 MIME-Version: 1.0 To: Apache Directory Developers List Subject: Re: Deploy apacheds in karaf and connect to it via apache directory studio References: <4E771D30.7030407@gmail.com> <4E78706E.4010909@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi Pierre-Arnaud, Thank you for your quick reply! I've tried with both 1.5.7 and 2.0.0-M3 release and the result is the same for both. I refer to 2.0.0-M3 now. Building the osgi artifact creates a bundle: org.apache.directory.server/apache-osgi/{whichever_version}. The osgi module, which was originally commented out in the parent pom, is described as: "Uncomment to build all in one OSGi bundle." I will be glad to provide you with more information and I also offer my help in moving ApacheDS to OSGI as I plan to use it for another project. Kind Regards, Christoph On 09/20/2011 12:58 PM, Pierre-Arnaud Marcelot wrote: > Hi Christoph, > > Which bundle are you talking about exactly? > > I'm asking this because, at this time, we have not done any work to move ApacheDS to OSGI. This is one of the tasks we're expecting tp do in a next milestone for the 2.0 release. > > At the moment only the Shared/LDAP API jars are constructed and work as bundles. > > Regards, > Pierre-Arnaud > > On 20 sept. 2011, at 12:52, Christoph Czurda wrote: > >> On 09/20/2011 07:12 AM, Alex Karasulu wrote: >>> On Mon, Sep 19, 2011 at 1:45 PM, Christoph Czurda >>> wrote: >>>> Hello! >>>> >>>> As already suggested by others on your mailing list, I would also be >>>> interested in deploying apacheds in karaf. So far I have been able to >>>> install the osgi feature, that is, I have the apacheds bundle in active >>>> state. Next, I wanted to see if this is sufficient to connect to the server >>>> using apache directory studio. It seems not. The bundle being active doesn't >>>> mean that the server is running and listening for connections, does it? >>>> >>>> What would be necessary to connect to the server? >>> Could u elaborate a bit more on how you configured ApacheDS in Karaf. >>> There's not enough information here to have traction for trouble >>> shooting your problem. First off can you telnet to the LDAP port ... >>> meaning establish a TCP connection, and which port exactly did you >>> configure the LDAP listener on? Many questions requiring more >>> information on how you configured ApacheDS to start in Karaf. >>> >> So far I did not configure anything at all. In Karaf I simply installed the provided features.xml found inside the osgi artifact (after adding a few missing dependencies). But the bundle being active does not open any new host and port I could connect to. >> >> Maybe I asked the wrong question... How can I start the server in Karaf? Or more generally: What does the OSGI bundle actually do? >> >> Thank you, >> Christoph