Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 83650 invoked from network); 30 May 2007 05:13:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 May 2007 05:13:17 -0000 Received: (qmail 31474 invoked by uid 500); 30 May 2007 05:13:21 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 31267 invoked by uid 500); 30 May 2007 05:13:20 -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 31250 invoked by uid 99); 30 May 2007 05:13:20 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 May 2007 22:13:20 -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.162.235 as permitted sender) Received: from [64.233.162.235] (HELO nz-out-0506.google.com) (64.233.162.235) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 May 2007 22:13:14 -0700 Received: by nz-out-0506.google.com with SMTP id i1so946053nzh for ; Tue, 29 May 2007 22:12:53 -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:mime-version:content-type:content-transfer-encoding:content-disposition; b=pbmmMwjm/PA9AbZI5Em++62Xhf/9NpPNubWTSyIQqPIk00udzqlFpd+bQZw2PUmXwBhou+fCN64tGewyLzKWa0FQUNEFQwGDnlUOZtgjdshZFWQuvjZYo/7IJpLFnex75RDKcj7b7Oj+mVAfoG8eMa8WnGTI7NT6jvIPAhjRAf8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=dw/EMWehoF6AwUReB5WcN0E17+U7+4nW5H4Nvb3xk3rg29pL9pPr6dEs7f6upukioEjfIMh7JBLBY83V3OKTVtwaiLeMXWjkhN/HRA2b/vq5EzxjP7lh47Fgzwbo+56oEbchdw40LPKGpYpHnc/HzM9/+c79vNYPpxFaJ9HQb/g= Received: by 10.114.154.1 with SMTP id b1mr3771116wae.1180501973440; Tue, 29 May 2007 22:12:53 -0700 (PDT) Received: by 10.115.111.11 with HTTP; Tue, 29 May 2007 22:12:53 -0700 (PDT) Message-ID: <568753d90705292212ya304284ve3819021195c8516@mail.gmail.com> Date: Tue, 29 May 2007 22:12:53 -0700 From: "Enrique Rodriguez" Reply-To: erodriguez@apache.org To: "Apache Directory Developers List" Subject: [LDAP] Parsing LDAP URLs MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org Hi, Directory developers, Do we already have support for searching based on LDAP URLs (RFC 2255)? Should a search with an LDAP URL using JNDI and CoreContextFactory "just work"? Example from the JNDI tutorial: Object obj = new InitialContext().lookup( "ldap://localhost:389/cn=homedir,cn=Jon%20Ruiz,ou=People,o=jnditutorial"); I'm especially interested in the more complex forms, where attribute values are specified. I haven't simply tried this but I'll get a chance later this week and I'm curious to know ASAP. Enrique