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 E24701897F for ; Mon, 12 Oct 2015 18:26:13 +0000 (UTC) Received: (qmail 54111 invoked by uid 500); 12 Oct 2015 18:26:13 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 54054 invoked by uid 500); 12 Oct 2015 18:26:13 -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 54044 invoked by uid 99); 12 Oct 2015 18:26:13 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Oct 2015 18:26:13 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id A468B180A65 for ; Mon, 12 Oct 2015 18:26:12 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.121 X-Spam-Level: X-Spam-Status: No, score=-0.121 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id hf7bCI29FNw7 for ; Mon, 12 Oct 2015 18:26:11 +0000 (UTC) Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 3BB9742F38 for ; Mon, 12 Oct 2015 18:26:11 +0000 (UTC) Received: by wicgb1 with SMTP id gb1so60592742wic.1 for ; Mon, 12 Oct 2015 11:26:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=to:from:subject:message-id:date:user-agent:mime-version :content-type:content-transfer-encoding; bh=dtRmBC6b64bsODYjoGBaz111eqwzDJTml3AtWmHu5To=; b=tfJTFJvAF/ERLQGnpjDo1BZi2jjLqkOlCHeVpAwzA3RCG/EbutUehs9yEYWtrrFu4K ozyikw4+gm4AGnQG2y7zRL/Z8whyP5clsC3nbarE66NvZ2XoX/OdEH2RRzbu8+H58Qnd f1Wcu5HCR0+jqE1ctZtu9hYYXEm23dIBPs0vOLjKkApJRnZtzqR8DULdPRhwoGUgHXh9 EvkNB+qMsz93DtBKWRJ7IFSV7xGcIdFph1wfwvs63ZMNsrYEnHZhQLB+KOOLLyHCLHB7 Y2fY4Y9sObwx5IJh1F5mhBOjNDmu3x72gYK01X+nJveoNK3qQhlSOyxtSo03MeGq8bAT jtKw== X-Received: by 10.194.240.4 with SMTP id vw4mr31679210wjc.89.1444674370189; Mon, 12 Oct 2015 11:26:10 -0700 (PDT) Received: from [172.20.10.3] ([80.12.39.168]) by smtp.googlemail.com with ESMTPSA id h6sm11825795wiy.14.2015.10.12.11.26.09 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 12 Oct 2015 11:26:09 -0700 (PDT) To: Apache Directory Developers List From: =?UTF-8?Q?Emmanuel_L=c3=a9charny?= Subject: Schema propagation in DN and issues in the server X-Enigmail-Draft-Status: N1110 Message-ID: <561BFB40.1000601@gmail.com> Date: Mon, 12 Oct 2015 20:26:08 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi guys, last week and most of this week-end, I was working on fixingthe way we propagate the SchemaManager in a DN (see conversation on api@directory.apache.org ML). The thing is that when we parse a DN and appky the schemaManager on it, this schemaManager was never propagated down to teh AVA and teh Value. As a reminder : DN -> RDN+ RDN -> AVA+ AVA -> AttributeType ':' Value Where Value can be either a StringValue or a BinaryValue. In all instances, we keep an UP vakue and a Norm value. The NormValue will be created applying the Normalizer fetched from the schema, accordingly to the AttributeType's Syntax. The API was not doing so, except at the RDN level (is, teh AVA and Value never get saw the SchemaManager). I have successfully changed the API to propagate the SchemaManager dow to the Ava and Value, which was quite a pain. In the process, I have found that *many* tests were simply plain wrong... Having fixed them was not the end of my pain :/ I just created an issue : https://issues.apache.org/jira/browse/DIRSERVER-1974 This is about a test in the server which is plain wrong : we try to rename an entry, providing a second RDN, expecting the new value being present in the entry within the old value (the deleteOldRdn flag is not set). And the test *passes*; never mind if the Attribute is a Single-Value attribute ! I'm trying to fix all those issues (and we have many), but that means we still have a lot of basic errors all around... More to come !