[
https://issues.apache.org/jira/browse/OAK-771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13907195#comment-13907195
]
Michael Dürig commented on OAK-771:
-----------------------------------
Fixed for core with OAK-1431. Also JCR doesn't have this issue since the name
validator takes care of validating item names.
[~tmueller], could you add a test case for the mongomk if this is still an
issue there. Otherwise I propose we resolve the issue as fixed.
> Correct behavior for strange node and property names
> ----------------------------------------------------
>
> Key: OAK-771
> URL: https://issues.apache.org/jira/browse/OAK-771
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, jcr, mongomk
> Reporter: Thomas Mueller
> Priority: Minor
>
> All components need to deal correctly with strange identifier names, for
> example umlauts, empty node or property names, slashes, dots (a problem for
> MongoDB), and so on. Some cases are legal, some not. Oak should throw an
> appropriate error message where needed.
> One case that doesn't work properly is trying to add a node named "" (empty
> node name) to the root node. In this case, the exception message is "node
> already exists". The message should probably be "illegal node name" or so.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
