You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2007/02/09 18:04:06 UTC

[jira] Reopened: (JCR-739) Predefined entity references are not decoded in string literal

     [ https://issues.apache.org/jira/browse/JCR-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Reutegger reopened JCR-739:
----------------------------------


Hmm, you are right. According to the XPath 2.0 syntax there are no entity references needed in string literals:

http://www.w3.org/TR/xpath20/#prod-xpath-StringLiteral

Jackrabbit uses a XQuery parser because of the order by extension defined in JSR 170 and there you need to encode the ampersand.

http://www.w3.org/TR/xquery/#doc-xquery-StringLiteral

Seems like the XQuery is not really a super set of XPath, even though it claims to be an extension to XPath.

> Predefined entity references are not decoded in string literal
> --------------------------------------------------------------
>
>                 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 entity reference is interpreted as is but should be decoded before the query is executed.
> Example:
> //element(*, nt:base)[jcr:contains(., 'max&amp;moritz')]

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.