[
https://issues.apache.org/jira/browse/JCR-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517964
]
Julian Reschke commented on JCR-1052:
-------------------------------------
Hm, I don't see a bug here.
It's correct that name escaping is a problem, but I don't see how Jackrabbit
can change that.
Maybe you could clarify?
> JCR valid names not allowed in Xpath xml sintax
> ------------------------------------------------
>
> Key: JCR-1052
> URL: https://issues.apache.org/jira/browse/JCR-1052
> Project: Jackrabbit
> Issue Type: Improvement
> Components: xpath
> Affects Versions: 1.3
> Environment: WIndows 2003/xp server/client
> Tomcat 6.0.x
> Reporter: Filippo Fratoni
>
> ref: JCR-579
>
> I'm working with Magnolia CMS that relies on Jackrabbit jcr Impl 1.3.
> I can't query valid JCR path using Jackrabbit SearchManager in xpath mode due
> to different spec. between JCR names and XML names.
> The ISO9075 approach in jackrabbit commons library is name based and not path
> based. The result is the need to parse again full path in an Xpath compliant
> way to recursively encode non XML names.
> I think that the owner of this enhancement should be SearchManager class or
> one of its collaborators(the parser for example) to ensure the consistence of
> JackRabbit jcr impl.
> For my project needs I'm going to token path string with "/" separator and
> then apply ISO9075 encode. It will be ok for my actual project.
> Thanks in advance
> Filippo
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
