[JCR-3366] incorrect handling of leading '{' in jcr names

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: jackrabbit-spi-commons
• Assignee: Unassigned
• Reporter: Stefan Guggisberg
• Created: 29/Jun/12 12:32
• Updated: 29/Jun/12 12:32

Description

the following code throws a (misleading) exception:

session.getRootNode().addNode("{foo");

the root cause of the exception is that "{foo" is not correctly parsed by

o.a.j.spi.commons.name.PathParser

PathParser.checkFormat("{foo")

succeeds,
but

PathParser.parse("{foo", resolver, factory)

throws a

MalformedPathException: empty path

NameParser

OTOH seems to correctly handle non-expandedform names with leading '{'.