Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
Description
When encountering names using index notation in storage, oak-jcr treats the index suffix as part of the name. This causes issues with other components that assume that the result of Node.getName() is indeed a valid JCR name.
Attachments
Attachments
Issue Links
- is related to
-
OAK-203 Basic same name sibling support
- Closed
-
JCRVLT-724 DocViewSaxFormatter: improve diagnostics when generating DocViewNode2 from JCR node
- Closed
-
JCR-4983 jackrabbit-spi-commons: improve diagnostics for invalid names
- Closed
There are no Sub-Tasks for this issue.