Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <20143512.1190121103544.JavaMail.jira@brutus>
Date: Tue, 18 Sep 2007 06:11:43 -0700 (PDT)
From: "Julian Reschke (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Commented: (JCR-522) XPath parser too tolerant
In-Reply-To: <6703403.1154178673920.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/JCR-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528378 ] 

Julian Reschke commented on JCR-522:
------------------------------------

Unfortunately there doesn't seem to be a test case checking this.

I apologize for breaking this, but the current state of things is clearly not optimal. There are many syntactically valid XPath queries that are neither understood nor rejected by the parser/query builder. The longer these kinds of bugs stay in there, the harder it may become to deploy fixes, once deployed code relies on them.

> XPath parser too tolerant
> -------------------------
>
>                 Key: JCR-522
>                 URL: https://issues.apache.org/jira/browse/JCR-522
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: query
>    Affects Versions: 0.9, 1.0, 1.0.1
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Minor
>
> The XPath parser seems to be too tolerant, in that it accepts expressions Jackrabbit is not designed to deal with, and silently treats them in some other way.
> For instance "/a | /b" is accepted and processed as "/a/b".
> (As mentioned on the mailing list, there may be other related issues such as unsupported function names that are accepted but shouldn't)

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