[
https://issues.apache.org/jira/browse/JCR-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthijs Wensveen updated JCR-1606:
-----------------------------------
Description:
When an xpath query uses the non-shorthand form of any xpath axis, it is
treated as 'child'.
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?
Of course, support for all axes would be great... :)
was:
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?
> 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'.
> 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?
> Of course, support for all axes would be great... :)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
