[
https://issues.apache.org/jira/browse/JCR-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15767021#comment-15767021
]
Julian Reschke commented on JCR-3800:
-------------------------------------
Proposal:
a) deprecate method
b) have a new method ("escapeForFullTextQuery()" ?) instead, which also
consistently escapes in all positions
Q: is the set of characters that needs to be escaped the same when in the
context of SQL syntax?
> Text.escapeIllegalXpathSearchChars escapes only last character
> --------------------------------------------------------------
>
> Key: JCR-3800
> URL: https://issues.apache.org/jira/browse/JCR-3800
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jcr-commons
> Affects Versions: 2.8
> Reporter: broman
>
> Escaping special characters by using Text.escapeIllegalXpathSearchChars works
> only on last special character.
> fullText = "Moving to Alabama? Start Off on the Left Foot!";
> println Text.escapeIllegalXpathSearchChars(fullText);
> Moving to Alabama? Start Off on the Left Foot\!
> fullText = "Moving to Alabama! Start Off on the Left Foot!";
> println Text.escapeIllegalXpathSearchChars(fullText);
> Moving to Alabama! Start Off on the Left Foot\!
> fullText = "Moving to Alabama! Start Off on the Left Foot?";
> println Text.escapeIllegalXpathSearchChars(fullText);
> Moving to Alabama! Start Off on the Left Foot\?
> And such partially escaped string cannot be used in full text search in JCR
> it doesn't throw errors but also doesn't return any nodes
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
