'OR' in XPath query badly interpreted
-------------------------------------
Key: JCR-562
URL: http://issues.apache.org/jira/browse/JCR-562
Project: Jackrabbit
Issue Type: Bug
Components: core
Affects Versions: 1.0.1
Reporter: Szymon Kuzniak
Attachments: tree.JPG
executing query: //[EMAIL PROTECTED] and @b=2 or @c=3] leads to creating wrong
query tree. The builded tree looks like for query: //[EMAIL PROTECTED] and @b=2
and @c=3](see attachement). using brackets resolves the problem, but without
brackets output query is different from input query. When AND and OR are
switched(so the OR is in first palce - //[EMAIL PROTECTED] or @b=2 and @c=3])
everything is ok.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
