You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Alexander Klimetschek (JIRA)" <ji...@apache.org> on 2016/11/10 07:10:58 UTC

[jira] [Commented] (OAK-5090) Provide escape/unescape utility for Oak node names

    [ https://issues.apache.org/jira/browse/OAK-5090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15653266#comment-15653266 ] 

Alexander Klimetschek commented on OAK-5090:
--------------------------------------------

Where should it go? IMO putting it into jackrabbit-api Text would be great in order to make it as visible as possible. Downside is that if the escaping needs to change in line with Oak versions, is that this would be a bit decoupled.

> Provide escape/unescape utility for Oak node names
> --------------------------------------------------
>
>                 Key: OAK-5090
>                 URL: https://issues.apache.org/jira/browse/OAK-5090
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: commons
>            Reporter: Alexander Klimetschek
>
> JCR applications often use [Text.escapeIllegalJcrChars()|https://jackrabbit.apache.org/api/2.8/org/apache/jackrabbit/util/Text.html#escapeIllegalJcrChars(java.lang.String)], but missing that Oak has more limits. There should be a common escape/unescape utility that covers all and ensures applications don't have problems with special characters.
> From OAK-4857, and related to OAK-5089 (documentation for the same). 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)