Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 85613 invoked from network); 8 Jul 2006 08:21:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 8 Jul 2006 08:21:23 -0000 Received: (qmail 32174 invoked by uid 500); 8 Jul 2006 08:21:22 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 32136 invoked by uid 500); 8 Jul 2006 08:21:22 -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 32125 invoked by uid 99); 8 Jul 2006 08:21:22 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Jul 2006 01:21:22 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Jul 2006 01:21:21 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 2BB9D41045E for ; Sat, 8 Jul 2006 08:19:30 +0000 (GMT) Message-ID: <24292480.1152346770161.JavaMail.jira@brutus> Date: Sat, 8 Jul 2006 08:19:30 +0000 (GMT+00:00) From: "Emmanuel Lecharny (JIRA)" To: dev@directory.apache.org Subject: [jira] Resolved: (DIR-115) Query string gets normilized in most cases (when normalization service is enabled) In-Reply-To: <445594043.1130958235809.JavaMail.jira@ajax.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/DIR-115?page=all ] Emmanuel Lecharny resolved DIR-115: ----------------------------------- Resolution: Won't Fix Assign To: Emmanuel Lecharny (was: Alex Karasulu) I assume that no answer means "yes" ... However, if needed, this issue can be reoppened. > Query string gets normilized in most cases (when normalization service is enabled) > ---------------------------------------------------------------------------------- > > Key: DIR-115 > URL: http://issues.apache.org/jira/browse/DIR-115 > Project: Directory > Type: Bug > Environment: N/A > Reporter: Giamma > Assignee: Emmanuel Lecharny > > I am submitting a query like this: > "cn=Joe Black" > When I process the query string from my custom partition, I get: > "cn=joe black" > How can I implement EQUALITY caseIgnoreMatch or EQUALITY caseExactMatch, if the original casing is gone ? > But when I run a query with a custom attribute, defined in the schema, the query string is not normailized. > All the logic seems to be in this class ValueNormalizingVisitor.visit(): > normalized = ncn.normalizeByName( snode.getAttribute(), snode.getValue() ); > ncn.normalizeByName will normalize for standard atttributes, but not for custom attributes added to the schema. > At the very least the code is not consistent. but I argue that it should not normilize the query string. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira