[
https://issues.apache.org/jira/browse/JCR-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518109
]
Filippo Fratoni commented on JCR-1052:
--------------------------------------
I'll send you in few days a complete tested solution for encoding xpath
query, my last attachment is just an example.
You can then decide to embedd it inside TokenManager or to expose it as
utility class.
I'll post it as soon as possible
> 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
> Attachments: Xpath_basic_encoding.txt
>
>
> 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.
