jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-327) Mixins as supertypes do not appear to be queryable
Date Fri, 24 Feb 2006 18:28:38 GMT
     [ http://issues.apache.org/jira/browse/JCR-327?page=all ]
Marcel Reutegger resolved JCR-327:

    Fix Version: 1.0
     Resolution: Fixed

There is indeed a bug in the query builder that creates the lucene query tree from the JCR
query statement.

Fixed in svn revision: 380766.

Thank you for reporting this issue.

Could you please check if this fix works for you and give a quick feedback? I did only check
it with existing predefined node types, but it should also works for any custom defined node

> Mixins as supertypes do not appear to be queryable
> --------------------------------------------------
>          Key: JCR-327
>          URL: http://issues.apache.org/jira/browse/JCR-327
>      Project: Jackrabbit
>         Type: Bug
>   Components: query, nodetype
>     Versions: 0.9
>     Reporter: Michael Daglian
>     Assignee: Marcel Reutegger
>      Fix For: 1.0
>  Attachments: MixinTypesTest.java, ntdefs.cnd
> When creating custom nodetypes that contain mixins as the supertype, nodes of the custom
type do not appear to be queryable when using statements of the form: //element(*, mixin).
Attached are a relatively simple JUnit test and compact type definition that seem to illustrate
the problem.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message