Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 79833 invoked from network); 18 May 2007 20:04:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 May 2007 20:04:41 -0000 Received: (qmail 35469 invoked by uid 500); 18 May 2007 20:04:32 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 35432 invoked by uid 500); 18 May 2007 20:04:32 -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 35404 invoked by uid 99); 18 May 2007 20:04:32 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 May 2007 13:04:32 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of enriquer9@gmail.com designates 64.233.184.226 as permitted sender) Received: from [64.233.184.226] (HELO wr-out-0506.google.com) (64.233.184.226) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 May 2007 13:04:26 -0700 Received: by wr-out-0506.google.com with SMTP id m59so1004929wrm for ; Fri, 18 May 2007 13:04:05 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=OgHJnK2n7n5DYvY7awP9Jo9pj5wGRv3zOrsLyDSvLW+oqaDVi+4Uu38IpN04+jq67IqeOfG24mNBonC3Za7nbqZgwpGHaNXFj7WuvFbdDqeJPVmDRfW07huX2l9sHE9gFdm2se8lgRPaRj5XY+cki5nTZjfwsi/AqCVmJ2SeE1k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=AYn5PPOC4xih27zDBQ42TLGrS46AeNQkXM9J8/a8kU9ne6LyzzIumzoPrmb3XyGZDdYP1kVBFyFhC7e1gxY4DPohMjVD6EGZimAgOgOleCU9tMcEs5peE4kg+f3AhsoabPa43+57fQO/ym82jNqaBcd3g1ego552b+ClKYcHLeY= Received: by 10.115.78.1 with SMTP id f1mr1063684wal.1179518645052; Fri, 18 May 2007 13:04:05 -0700 (PDT) Received: by 10.115.111.11 with HTTP; Fri, 18 May 2007 13:04:04 -0700 (PDT) Message-ID: <568753d90705181304m36b8f5cdidb7639e5ccfa3737@mail.gmail.com> Date: Fri, 18 May 2007 13:04:04 -0700 From: "Enrique Rodriguez" Reply-To: erodriguez@apache.org To: "Apache Directory Developers List" Subject: Re: [ApacheDS] SASL Branch In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <568753d90705181230p5a07700fg75b5c73f375f5b69@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org On 5/18/07, Alex Karasulu wrote: > Oh and btw some services like the HTTP service which will use Jetty or > Tomcat > is really not a MINA service. I guess in this case we should not use the > ServiceConfiguration > bean as the extended bean right? Correct. Likely they have their own mechanisms for configuration. We developed these protocols here, so we are doing raw config. > Perhaps what you mean by > ServiceConfiguration is really a > MinaServiceConfiguration? They happen to all use MINA, but really the distinction here is that they are all our own protocols. The HTTP implementations (Jetty, Tomcat) aren't ours and so wouldn't use our specific configuration setup. The HTTP's may have their own Spring beans already. In any case, you are right that they wouldn't extend our ServiceConfiguration. Enrique