You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2007/02/09 16:51:05 UTC
[jira] Commented: (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:comment-tabpanel#action_12471730 ]
Julian Reschke commented on JCR-739:
------------------------------------
Is this on the level of the JCR API?
Why would we want to decode entity references here? Entity references need to be considered when the query string is represented in XML, but here...?
> 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&moritz')]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.