[JCR-739] String literal must not interpret entity references

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.9, 1.0, 1.0.1, 1.1, 1.1.1, 1.2.1
• Fix Version/s: 1.3
• Component/s: query
• Assignee: Marcel Reutegger
• Reporter: Marcel Reutegger
• Created: 09/Feb/07 13:13
• Updated: 25/Apr/07 08:45
• Resolved: 12/Feb/07 09:14

Description

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.

Issue Links

• is duplicated by: JCR-834 Ampersand In query constraint causes InvalidQueryException