Return-Path: 
 <jackrabbit-dev-return-4651-apmail-incubator-jackrabbit-dev-archive=www.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-jackrabbit-dev-archive@www.apache.org
Received: (qmail 62750 invoked from network); 1 Dec 2005 10:24:55 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 1 Dec 2005 10:24:55 -0000
Received: (qmail 46928 invoked by uid 500); 1 Dec 2005 10:24:53 -0000
Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:jackrabbit-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:jackrabbit-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:jackrabbit-dev@incubator.apache.org>
List-Id: <jackrabbit-dev.incubator.apache.org>
Reply-To: jackrabbit-dev@incubator.apache.org
Delivered-To: mailing list jackrabbit-dev@incubator.apache.org
Received: (qmail 46917 invoked by uid 99); 1 Dec 2005 10:24:53 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Dec 2005 02:24:53 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of peeter.piegaze@gmail.com
 designates 64.233.162.207 as permitted sender)
Received: from [64.233.162.207] (HELO zproxy.gmail.com) (64.233.162.207)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Dec 2005 02:26:21 -0800
Received: by zproxy.gmail.com with SMTP id s1so261844nze
        for <jackrabbit-dev@incubator.apache.org>;
 Thu, 01 Dec 2005 02:24:31 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=YNCcSSt5hDHUxUInVEn8CuUEgR1N+tgpbT8lXXIemLt4sq9yoUK/rQkaQofFNIPvQWm3BQl2Yj0xEF0pxa7+SnzFWfFC0PTJkxajv2FSOcoRkn89HHhDPYqEYfJQQXIYZB3e0QLIHPnkHYIysHEHsTEoxlTIhybUKzWNoXbrgXM=
Received: by 10.64.196.9 with SMTP id t9mr734488qbf;
        Thu, 01 Dec 2005 02:24:31 -0800 (PST)
Received: by 10.65.181.3 with HTTP; Thu, 1 Dec 2005 02:24:31 -0800 (PST)
Message-ID: <3df33a250512010224n1c63aabr32bfb6335ea2db96@mail.gmail.com>
Date: Thu, 1 Dec 2005 11:24:31 +0100
From: Peeter Piegaze <peeter.piegaze@day.com>
Sender: peeter.piegaze@gmail.com
To: jackrabbit-dev@incubator.apache.org
Subject: Re: TCK: multivalue
In-Reply-To: <90a8d1c00512010157u1ca3082k621d7bcfc5c52be7@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <005301c5f5b6$052dfc80$bb0e020a@Gennady>
	 <90a8d1c00511300608p3e009560sabd05272bba0962f@mail.gmail.com>
	 <007001c5f5c8$74fe14c0$bb0e020a@Gennady>
	 <90a8d1c00511300904m74f74e60s6842d99c54e3c3ad@mail.gmail.com>
	 <008701c5f644$25ff3b20$bb0e020a@Gennady>
	 <90a8d1c00512010157u1ca3082k621d7bcfc5c52be7@mail.gmail.com>
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Hi Gennady,

You wrote:

> sorry, i just cant find clear definition in the specs and want to know th=
is
> matter for sure as i experienced some difficulties in implementation and =
testing :)

As Stefan points out, the spec is quite clear on this issue. The
PropertyDefinition is "sticky". It is determined once on property
creation and that's it. Therefore the TCK test is correct. See the
Javadoc box for Property.getDefinition in section 6.7.18 of the spec:

<quote>
PropertyDefinition Property.getDefinition()

Returns the property definition that applies to this Property. In some
cases there may appear to be more than one definition that could apply
to this property. However, it is assumed that upon creation of this
property, a single particular definition was used and it is that
definition that this method returns. How this governing definition is
selected upon property creation from among others which may have been
applicable is an implementation issue and is not covered by this
specification.

Throws a RepositoryException if an error occurs.
</quote>

Notice that from an implementation point of view this is a simplifying
restriction in that you are not permitted to dynamically re-associate
properties with property definitions after creation. Presumably this
makes your job easier, not harder, right?

Cheers,
Peeter