Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 39356 invoked from network); 21 Jun 2005 04:36:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 21 Jun 2005 04:36:05 -0000 Received: (qmail 40944 invoked by uid 500); 21 Jun 2005 04:36:05 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 40904 invoked by uid 500); 21 Jun 2005 04:36:04 -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 40888 invoked by uid 99); 21 Jun 2005 04:36:03 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Jun 2005 21:36:03 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=RCVD_BY_IP X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of trustin@gmail.com designates 64.233.184.197 as permitted sender) Received: from [64.233.184.197] (HELO wproxy.gmail.com) (64.233.184.197) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Jun 2005 21:36:05 -0700 Received: by wproxy.gmail.com with SMTP id 70so1026790wra for ; Mon, 20 Jun 2005 21:36:02 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=V2IhWasI//R5hqlN9JHWEwsGByF80MWhGw6ZfsXoTO1wLHds6s1OtwxC6nI9qZeBSXNUcBKpr6VzdZjWGZrEcMJszpPwNzkuADpCHnA1UkqbXC7aAOeIVbZLJs7WrOvFxblaP0LdOtXkn8mG3TDjsmM2XCt0iXZOZftpj/cw6V4= Received: by 10.54.68.14 with SMTP id q14mr3100015wra; Mon, 20 Jun 2005 21:36:02 -0700 (PDT) Received: by 10.54.72.4 with HTTP; Mon, 20 Jun 2005 21:36:01 -0700 (PDT) Message-ID: <768dcb2e05062021366d786c3@mail.gmail.com> Date: Tue, 21 Jun 2005 13:36:01 +0900 From: Trustin Lee Reply-To: Trustin Lee To: Apache Directory Developers List Subject: Re: is a org.apache.ldap.server.configuration.Configuration required in every JNDI connection? In-Reply-To: <42B78086.90602@atlassian.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <42B667A9.5030206@atlassian.com> <42B7333E.1010801@bellsouth.net> <768dcb2e050620170734975104@mail.gmail.com> <42B78086.90602@atlassian.com> X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I checked in the fix. Could you try to build apacheds-core? You shouldn't need to put SyncConfiguration now. Trustin 2005/6/21, Nick Faiz : > Hi Trustin, > Thanks for the quick response. >=20 > Yes, there's no immediate problem here for federation. I realise now > that there's no problem in having to gain access to the original > Configuration object when creating a new JNDI context each time. I can > simply create a new SyncConfiguration() each time. Trustin --=20 what we call human nature is actually human habit -- http://gleamynode.net/