jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Serge Huber (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-100) contrib/orm-persistence Node ordering not supported
Date Thu, 07 Apr 2005 10:18:48 GMT
     [ http://issues.apache.org/jira/browse/JCR-100?page=history ]

Serge Huber updated JCR-100:

    Attachment: orm-20050407-1150-fix-nodeordering.patch

This patch solves the bug, please apply ASAP.

> contrib/orm-persistence Node ordering not supported
> ---------------------------------------------------
>          Key: JCR-100
>          URL: http://issues.apache.org/jira/browse/JCR-100
>      Project: Jackrabbit
>         Type: Bug
>     Reporter: Serge Huber
>     Priority: Minor
>  Attachments: orm-20050407-1150-fix-nodeordering.patch
> Due to a limitation in the implementation, node ordering isn't supported (it is optional
in the specification but Jackrabbit provides support for it) in the ORM persistence manager.
This is due to the fact that in the database, although same-name sibling ordering is supported,
no guarantee is given for the ordering of nodes in the child list.
> Jackrabbit has some tests that use node ordering, such as the DerefQueryLevel1Test, where
we look for the first property of type reference by using the following code :
>         Property refProp = PropertyUtil.searchProp(session, testRootNode, PropertyType.REFERENCE);
> The searchProp method traverses the tree and stops at the first property of the type
specified. If node ordering is not correct, we return a property that is not the expected
one (in the case of the DerefTest we were returning a multi-values reference property), which
can could test failures.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message