jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Bocanegra" <tobias.bocane...@day.com>
Subject Re: Ordering child nodes across node types
Date Thu, 05 Apr 2007 19:30:27 GMT
hi,
the "orderable" actually means: "orderable child nodes", i.e. it
refers to the parent node. in your example, if A is of type "myType"
you should be able to order the child nodes no matter what nodetype
they are.

are you sure, node A is defined correctly?
regards, toby

On 4/5/07, James Hang <jhang@bea.com> wrote:
>
> I have the following mixin type "myMixin":
>
> [myMixin] mixin orderable
> + mixA (someType)
> + mixB (someType)
>
> I have the following node type "myType" which includes "mix":
>
> [myType] > myMixin orderable
> + typeA
> + typeB
>
> So I can create a new node A of type "myType" and add the following child
> nodes:
>
> A --> mixA, mixB, typeA, typeB
>
> However, when I try to re-order "typeA" before "mixB", I get "child node
> ordering not supported" error even though both "myType" and "myMixin" are
> defined with the "orderable" keyword.  Is it because "typeA" and "mixB" are
> in different types and so you can't order between them?  If so, is there a
> way around this?
>
> --
> View this message in context: http://www.nabble.com/Ordering-child-nodes-across-node-types-tf3532735.html#a9859825
> Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
>
>


-- 
-----------------------------------------< tobias.bocanegra@day.com >---
Tobias Bocanegra, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel
T +41 61 226 98 98, F +41 61 226 98 97
-----------------------------------------------< http://www.day.com >---

Mime
View raw message