Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (nike.apache.org: domain of pajbam@gmail.com designates
 74.125.82.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=sender:content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=k/jPfwHb2bjR8IWaSxtuKhOg4XZXaZFvjmBAoR7uyP0UZx2Hka1+Y0fuxyYDiRfumX
         vkgBLuQTbHiSpDzi+2vIuFvFT1HFlIxqxBlSqh7p1FVTusv5u0QPDnH2g5UV5ArR1qNn
         WBNzlrPrnhZ1No4P3c1XpnhQN+7tvrmSqIlpQ=
Sender: Pierre-Arnaud Marcelot <pajbam@gmail.com>
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: Should modifications made on cn=schema stored on disk ?
From: Pierre-Arnaud Marcelot <pa@marcelot.net>
In-Reply-To: <9F00E91A-BAA4-4DD3-A6C4-319C7229F472@marcelot.net>
Date: Fri, 14 Jan 2011 10:41:48 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <2E643E87-49A4-401E-9766-BF1C1527DABF@marcelot.net>
References: <4D300356.4060302@gmail.com>
 <1890E54A-DDBB-45FF-B50F-D5303451D2A4@marcelot.net>
 <4D30162B.9030703@gmail.com>
 <9F00E91A-BAA4-4DD3-A6C4-319C7229F472@marcelot.net>
To: Apache Directory Developers List <dev@directory.apache.org>

Maven 3.0.2 installed.

Same warnings...

Regards,
Pierre-Arnaud
=09
On 14 janv. 2011, at 10:37, Pierre-Arnaud Marcelot wrote:

>=20
> On 14 janv. 2011, at 10:23, Emmanuel Lecharny wrote:
>=20
>> On 1/14/11 9:58 AM, Pierre-Arnaud Marcelot wrote:
>>> Hi Emmanuel,
>>>=20
>>> I think it should.
>>>=20
>>> In the current state, does this mean that any modification done on =
ou=3Dschema will not be saved and will be lost if the server is =
rebooted?
>>=20
>> No, modifications done on ou=3Dschema are persisted on disk. Only the =
modifications done on cn=3Dschema are not persisted, AFAICT.
>=20
> Hum... I'm confused...
> You just said the opposite in your first mail: "[...] modification is =
not stored on disk in ou=3Dschema"...
>=20
>> I'll create a JIRA and a test to demonstrate the issue.
>>=20
>> Fixing it should not be a problem, it's just a a matter of converting =
the schema element (which is passed using the schema element syntax) to =
a meta-schema entry, and propagate it to the backend.
>>=20
>> Remember that modifications to cn=3Dschema are *not* allowed (it's a =
read only data structure) from outside the server, but it's always =
possible to modify the rootDSE subschemaSubentry attribute, as it =
contains all the loaded schema element. This will, in fact, impact the =
cn=3Dschema, as it's just a LDAP exposition of the loaded schema.
>=20
> Hum... I'm confused again...
> To my knowledge, 'subschemaSubentry' attribute value points to the =
"cn=3Dschema" DN and that's in this particular entry that you can access =
the schema elements (via 'attributeTypes', 'comparators', [etc.] =
attributes).
> I'm 100% sure 'subschemaSubentry' attribute does not contain any =
loaded schema element.
>=20
>>=20
>>=20
>> --=20
>> Regards,
>> Cordialement,
>> Emmanuel L=E9charny
>> www.iktek.com
>>=20
>=20