Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: domain of jukka.zitting@gmail.com
 designates 209.85.212.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5051B3C1.9050404@gmx.de>
References: 
 <9C0FC4C8E9C29945B01766FC7F9D389816FE0B22BF@eurmbx01.eur.adobe.com>
 <CAOFYJNbEU59LLJVBe3rA5_NRB1u74oVAOTnr0hj3Thzg2dUM5Q@mail.gmail.com>
 <5051B3C1.9050404@gmx.de>
From: Jukka Zitting <jukka.zitting@gmail.com>
Date: Thu, 13 Sep 2012 12:28:59 +0200
Message-ID: 
 <CAOFYJNYHQ8KjDYmumah_U6LBjxzsNsvXgE3Unr=ZqZtY0_70ag@mail.gmail.com>
Subject: Re: namespace remapping
To: Oak devs <oak-dev@jackrabbit.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

Hi,

On Thu, Sep 13, 2012 at 12:21 PM, Julian Reschke <julian.reschke@gmx.de> wrote:
> On 2012-09-13 11:10, Jukka Zitting wrote:
>> The idea, not implemented yet, of how such things should be handled is
>> to have a commit hook that looks out for changes in registered
>> namespace prefixes and either a) simply rejects them, or b) goes
>> through all existing content (potentially with a query to save time)
>> and automatically updates all names and paths that contain modified
>
> We could do that for node names and some type of property values. But it
> would still potentially break other things (link identifiers in content,
> think a/@href).

Such content (value types other than NAME, PATH, etc.) is in any case
outside the scope of what the repository can be expected to do.
Remapping a namespace prefix in Jackrabbit 2.x won't affect such
content either.

BR,

Jukka Zitting