Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of mueller@adobe.com designates
 64.18.1.39 as permitted sender)
From: Thomas Mueller <mueller@adobe.com>
To: "oak-dev@jackrabbit.apache.org" <oak-dev@jackrabbit.apache.org>
Date: Thu, 10 May 2012 08:34:30 +0100
Subject: Re: value conversions, and relative paths in Oak
Thread-Topic: value conversions, and relative paths in Oak
Thread-Index: Ac0uf1gvK87GZSlHQNyVNrTn5usPsQ==
Message-ID: <CBD13BA2.2BAA7%mueller@adobe.com>
In-Reply-To: <4FAB6459.1030204@adobe.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.2.1.120420
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi,

>>1) missing Date->long/double/decimal value conversions. I have added
>> those for now in ValueImpl (not core); is this correct, Angela?
>
>as long as we don't need it in the core, i would add it in oak-jcr.
>we can still push i down to the CoreValue later on.

Value conversions are (or at least will be) used in the query engine, in
oak-core.

>the basic question is again what part of the validation should be
>in which layer... that's a matter of definition rather than right
>or wrong.

I thought it's about converting not validation

Regards,
Thomas