Re: non-space whitespace in name

Hi >From a user's perspective, it concerns me that item names are being changed >when migrating from Jackrabbit (2) to Oak (Jackrabbit 3) … This may (or may >not) cause applications to mysteriously break. Just my $.02 to consider — not a requirement to change OAK-1624 Regards Felix Am 13.06.2

Re: non-space whitespace in name

Hi >From a user's perspective, it concerns me that item names are being changed >when migrating from Jackrabbit (2) to Oak (Jackrabbit 3) … This may (or may >not) cause applications to mysteriously break. Just my $.02 to consider — not a requirement to change OAK-1624 Regards Felix Am 13.06.2

Re: non-space whitespace in name

On Fri, Jun 13, 2014 at 6:51 AM, Julian Reschke wrote: > On 2014-06-13 15:37, Tobias Bocanegra wrote: >> >> On Thu, Jun 12, 2014 at 10:55 PM, Julian Reschke >> wrote: >>> >>> On 2014-06-13 02:14, Tobias Bocanegra wrote: Hi, according to [0] oak does not allow a non-space

Re: non-space whitespace in name

Hi, On Thu, Jun 12, 2014 at 8:14 PM, Tobias Bocanegra wrote: > according to [0] oak does not allow a non-space whitespace in the > name. this is different than in jackrabbit. also it should be allowed > based on [1]. We intentionally apply stricter name rules than what the spec allows. See the d

Re: non-space whitespace in name

On 2014-06-13 15:37, Tobias Bocanegra wrote: On Thu, Jun 12, 2014 at 10:55 PM, Julian Reschke wrote: On 2014-06-13 02:14, Tobias Bocanegra wrote: Hi, according to [0] oak does not allow a non-space whitespace in the name. this is different than in jackrabbit. also it should be allowed based

Re: non-space whitespace in name

On Thu, Jun 12, 2014 at 10:55 PM, Julian Reschke wrote: > On 2014-06-13 02:14, Tobias Bocanegra wrote: >> >> Hi, >> >> according to [0] oak does not allow a non-space whitespace in the >> name. this is different than in jackrabbit. also it should be allowed >> based on [1]. >> >> the problem at ha

Re: non-space whitespace in name

On 2014-06-13 02:14, Tobias Bocanegra wrote: Hi, according to [0] oak does not allow a non-space whitespace in the name. this is different than in jackrabbit. also it should be allowed based on [1]. the problem at hand is, that we have content with 'no-break-space' chars in node names, that doe

non-space whitespace in name

Hi, according to [0] oak does not allow a non-space whitespace in the name. this is different than in jackrabbit. also it should be allowed based on [1]. the problem at hand is, that we have content with 'no-break-space' chars in node names, that doesn't install in oak anymore. regards, toby [0