You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Thomas Mueller (JIRA)" <ji...@apache.org> on 2014/01/07 09:49:50 UTC

[jira] [Commented] (OAK-1304) createQuery(query,Query.JCR_JQOM) is returning QueryImpl instead of QueryObjectModel

    [ https://issues.apache.org/jira/browse/OAK-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13864013#comment-13864013 ] 

Thomas Mueller commented on OAK-1304:
-------------------------------------

You are right, the spec requires this. I wasn't actually aware about that. I think there are no tests in Jackrabbit 2.x about it.

If we want to support it in Oak: Implementing it would require a SQL-2 parser in oak-jcr, so there would be some code duplication, as there is already a SQL-2 parser, in oak-core. The parser in oak-core can't be used because it doesn't return in a QOM tree but an AST. Also, the parser in oak-core is more powerful (it supports features that can't be mapped to a QOM tree). In this case, I think it would be better to duplicate the code.

> createQuery(query,Query.JCR_JQOM) is returning QueryImpl  instead of QueryObjectModel
> -------------------------------------------------------------------------------------
>
>                 Key: OAK-1304
>                 URL: https://issues.apache.org/jira/browse/OAK-1304
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: jcr
>            Reporter: Vijay Kumar j
>
> createQuery(query,Query.JCR_JQOM) is returning QueryImpl  instead of QueryObjectModel
> According to the spec queryManager implementation will return an instance of QueryObjectModel when passing Query.JCR_JQOM as the language.
> http://www.day.com/specs/jcr/2.0/6_Query.html#6.9%20Query%20Object
> http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/javax/jcr/query/QueryManager.html



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)