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 jukka.zitting@gmail.com
 designates 209.85.198.224 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=JUwkZqEzdC5COtCeGiMym56fNamjB2ZRMkNULZcDP2t3cBA4i97+mMLfXBi+6S/QSD
         WtZqNPcQdeEDvkPDwy0T9lnbrVJVoTjhQJAD3K3OyPiq8ZlqACVND2tRekPeG7u6cTXX
         n34lgKNziTzjdfzHEeoZsdCug5ZPq04L8hwmM=
Message-ID: <510143ac0811200909q70c15276y827f7aaeef0bac32@mail.gmail.com>
Date: Thu, 20 Nov 2008 18:09:39 +0100
From: "Jukka Zitting" <jukka.zitting@gmail.com>
To: users@jackrabbit.apache.org
Subject: Re: System View XML mapping and multivalued properties
In-Reply-To: <FC826B34-E6BB-4667-8127-2573967D447E@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <FC826B34-E6BB-4667-8127-2573967D447E@gmail.com>

Hi,

On Thu, Nov 20, 2008 at 5:29 PM, Alessandro Bologna
<alessandro.bologna@gmail.com> wrote:
> Maybe I am missing something, but if that's the case that I am not, maybe it
> would be worth adding some implementation specific workaround, such as
> adding an optional sv:multivalued="true" attribute that then can be used
> transparently during import. It should not break anything I believe (unless
> there's some strict validation of the SV schema in place).

You're right, the spec is incomplete in that case and the only thing
we could do for now is to add some implementation-specific multivalue
marker. See also https://issues.apache.org/jira/browse/JCR-1464.

BR,

Jukka Zitting