Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <48811460.1210877097219.JavaMail.jira@brutus>
Date: Thu, 15 May 2008 11:44:57 -0700 (PDT)
From: "Matthijs Wensveen (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Created: (JCR-1606) Throw exception when unsupported xpath
 axes are used.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Throw exception when unsupported xpath axes are used.
-----------------------------------------------------

                 Key: JCR-1606
                 URL: https://issues.apache.org/jira/browse/JCR-1606
             Project: Jackrabbit
          Issue Type: New Feature
            Reporter: Matthijs Wensveen


When an xpath query uses the non-shorthand form of any xpath axis, it is treated as 'child'. The shorthand form of 'descendant-or-self' does work though. For example: '/*//*' does not yield the same results as '/*/descendant::*' while being equivalent.

According to the JCR 1.0.1 specification, only the abbreviated syntax need to be supported. However, I can't find what should happen when unsupported xpath features are used. It would be usefull when some exception is thrown, for example the InvalidQueryException?

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