jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Julian Reschke <julian.resc...@gmx.de>
Subject Re: value conversions, and relative paths in Oak
Date Thu, 10 May 2012 07:54:49 GMT
On 2012-05-10 08:46, Angela Schreiber wrote:
> hi julian
>
>> 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.

That's where I put it for now.

> 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.
>
>> 2) we didn't round-trip a relative path of ".". Now we do, but I'm not
>> sure I got the mapping correct. What is a same-node reference in Oak
>> path syntax? "." or empty string?
>
> well, i would expect "."

Indeed.

>> I also fear that we need to be able to
>> round-trip relative paths like "../foo/bar" in path values, which we
>> currently do not. Do we need a "normalize" flag???
>
> i would expect that we need it sooner or later.

+1

>> 3) Node.getNode(".") failed because it looked for a child called ".". If
>> have added a hack to make this work, but I'm wondering how to do this
>> properly.
>
> imo oak paths should always be normalized except for path values.

Which means that we need to expose that in the path mapping API, right?

Mime
View raw message