jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Guggisberg <stefan.guggisb...@gmail.com>
Subject Re: Special characters in JCR Node names
Date Fri, 29 Jun 2012 12:36:10 GMT
On Thu, Jun 28, 2012 at 10:18 AM, Julian Reschke <julian.reschke@gmx.de> wrote:
> On 2012-06-28 09:57, Stefan Guggisberg wrote:
>>
>> On Wed, Jun 27, 2012 at 10:37 PM, juser <jchacko@maned.com> wrote:
>>>
>>> Does anyone know the list of special characters not allowed in Jackrabbit
>>> node names?
>>> For example, when we use a node name like {}*|[]:/   all the characters
>>> except {} are escaped.
>>>
>>> {m is not accepted as a node name and it rerturns a Repository exception
>>> like "Failed to resolve path {m relative to node /pnode/bnode".
>>>
>>> But m} is accepted as a nodename, and doesn't throw any exceptions.
>>>
>>> Could you please list out the special characters disallowed in Jackrabbit
>>> repository?
>>
>>
>> see [0].
>>
>> if a name starts with a '{' the name is expected to be in the
>> 'Expanded Form'. see [1].
>> ...
>
>
> That is misleading. "{" is only special when the name conforms to the
> expanded name ABNF, so it MUST be followed by a URI and a "}". That's why we
> could introduce the notation in JCR 2.0 in the first place (all previously
> legal names stay valid).
>
> I believe this is simply a bug in Jackrabbit.

yes, you're right. i created an issue [0].

cheers
stefan

[0] https://issues.apache.org/jira/browse/JCR-3366

>
> Best regards, Julian

Mime
View raw message