Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of mrduguo@gmail.com designates
 72.14.220.157 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=EoG02feijpqXeH5o7WmjKMhFg4ytIcmSzMjRzPND6umtFj7hmhZ4o0i/MkjmnqmzD0
         eCUFu8oQawKQJkZQwoYwWegE5OTwZqtJ6HP6dJDC+MZvhrIafRBTm23N2p1B9NFh7VAl
         1Ow3jqZLML8A43h9RyKCoP4GmsEOoqjXAu+qc=
MIME-Version: 1.0
In-Reply-To: <f767f0600911160449j617c3976kf07e85660f84f30e@mail.gmail.com>
References: <AA62724B-616D-4243-B867-6651D33B19F1@maya-systems.com>
	 <ffd6aaa90911131421k412ddf94w1bfbe5521a05030f@mail.gmail.com>
	 <f767f0600911160449j617c3976kf07e85660f84f30e@mail.gmail.com>
Date: Mon, 16 Nov 2009 13:45:41 +0000
Message-ID: <e2a35cbc0911160545r7c07e29fve37c40074d875ce1@mail.gmail.com>
Subject: Re: David's Model question : nt:unstructured and SNS
From: Guo Du <mrduguo@gmail.com>
To: users@jackrabbit.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Nov 16, 2009 at 12:49 PM, Bertrand Delacretaz
<bdelacretaz@apache.org> wrote:
> Although that would be non-standard w.r.t JCR, I think such a "don't
> accept same-name siblings" configuration flag might be useful. It is
> relatively easy to end up with same-name siblings without really
> meaning to.

I don't think a system wide flag to disable SNS is possible. As there
are some system nodes in jcr:system come with same-name siblings.

A custom node definition could solve this problem by design, I
couldn't see the problem here.

-Guo