[
https://issues.apache.org/jira/browse/JCR-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger resolved JCR-739.
----------------------------------
Resolution: Fixed
Changed the strip.xsl to special-case the StringLiteral token and ignore the
entity references.
Also regenerated and committed the XPath.jjt file.
Fixed in revision: 506382
> String literal must not interpret entity references
> ---------------------------------------------------
>
> Key: JCR-739
> URL: https://issues.apache.org/jira/browse/JCR-739
> Project: Jackrabbit
> Issue Type: Bug
> Components: query
> Affects Versions: 0.9, 1.0, 1.0.1, 1.1, 1.1.1, 1.2.1
> Reporter: Marcel Reutegger
> Assigned To: Marcel Reutegger
> Priority: Minor
> Fix For: 1.3
>
>
> The ampersand character in a string literal is interpreted as a start
> character for an entity reference. This is because Jackrabbit uses an XQuery
> parser where a string literal is slightly more constraint than in XPath.
> Example:
> //element(*, nt:base)[jcr:contains(., 'max&moritz')]
> throws a parse exception. Instead the parser should simply recognize the
> ampersand as regular character.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
