You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by James Hang <jh...@bea.com> on 2006/12/14 01:01:01 UTC
Non-orderable child nodes
How does Jackrabbit handle non-orderable child nodes? e.g. when you call
Node.getNodes() on a non-orderable node, does it return the nodes in a
random order? Can the order change at any time?
--
View this message in context: http://www.nabble.com/Non-orderable-child-nodes-tf2817547.html#a7864219
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
Re: Non-orderable child nodes
Posted by Stefan Guggisberg <st...@gmail.com>.
On 12/14/06, James Hang <jh...@bea.com> wrote:
>
> So there's no real benefit on making child nodes non-orderable, e.g. no
> performance gains?
no, not in jackrabbit.
i'd rephrase your statement as follows:
in jackrabbit there's no performance loss when making child nodes orderable.
cheers
stefan
>
>
> Stefan Guggisberg wrote:
> >
> > On 12/14/06, James Hang <jh...@bea.com> wrote:
> >>
> >> How does Jackrabbit handle non-orderable child nodes? e.g. when you call
> >> Node.getNodes() on a non-orderable node, does it return the nodes in a
> >> random order? Can the order change at any time?
> >
> > it's implementation dependant according to "4.4.2 Non-orderable Child
> > Nodes"
> > of the jsr 170 spec. in jackrabbit the order of non-orderable child nodes
> > is preserved, internally there's no difference between orderable and
> > non-orderable child nodes.
> >
> > cheers
> > stefan
> >
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Non-orderable-child-nodes-tf2817547.html#a7864219
> >> Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
> >>
> >>
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Non-orderable-child-nodes-tf2817547.html#a7878698
> Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
>
>
Re: Non-orderable child nodes
Posted by Michael Neale <mi...@gmail.com>.
no in jackrabbit as of NOW, but in future, or with another JCR
implementation, could well make a difference.
On 12/14/06, James Hang <jh...@bea.com> wrote:
>
>
> So there's no real benefit on making child nodes non-orderable, e.g. no
> performance gains?
>
>
> Stefan Guggisberg wrote:
> >
> > On 12/14/06, James Hang <jh...@bea.com> wrote:
> >>
> >> How does Jackrabbit handle non-orderable child nodes? e.g. when you
> call
> >> Node.getNodes() on a non-orderable node, does it return the nodes in a
> >> random order? Can the order change at any time?
> >
> > it's implementation dependant according to "4.4.2 Non-orderable Child
> > Nodes"
> > of the jsr 170 spec. in jackrabbit the order of non-orderable child
> nodes
> > is preserved, internally there's no difference between orderable and
> > non-orderable child nodes.
> >
> > cheers
> > stefan
> >
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Non-orderable-child-nodes-tf2817547.html#a7864219
> >> Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Non-orderable-child-nodes-tf2817547.html#a7878698
> Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
>
>
Re: Non-orderable child nodes
Posted by James Hang <jh...@bea.com>.
So there's no real benefit on making child nodes non-orderable, e.g. no
performance gains?
Stefan Guggisberg wrote:
>
> On 12/14/06, James Hang <jh...@bea.com> wrote:
>>
>> How does Jackrabbit handle non-orderable child nodes? e.g. when you call
>> Node.getNodes() on a non-orderable node, does it return the nodes in a
>> random order? Can the order change at any time?
>
> it's implementation dependant according to "4.4.2 Non-orderable Child
> Nodes"
> of the jsr 170 spec. in jackrabbit the order of non-orderable child nodes
> is preserved, internally there's no difference between orderable and
> non-orderable child nodes.
>
> cheers
> stefan
>
>> --
>> View this message in context:
>> http://www.nabble.com/Non-orderable-child-nodes-tf2817547.html#a7864219
>> Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Non-orderable-child-nodes-tf2817547.html#a7878698
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
Re: Non-orderable child nodes
Posted by Stefan Guggisberg <st...@gmail.com>.
On 12/14/06, James Hang <jh...@bea.com> wrote:
>
> How does Jackrabbit handle non-orderable child nodes? e.g. when you call
> Node.getNodes() on a non-orderable node, does it return the nodes in a
> random order? Can the order change at any time?
it's implementation dependant according to "4.4.2 Non-orderable Child Nodes"
of the jsr 170 spec. in jackrabbit the order of non-orderable child nodes
is preserved, internally there's no difference between orderable and
non-orderable child nodes.
cheers
stefan
> --
> View this message in context: http://www.nabble.com/Non-orderable-child-nodes-tf2817547.html#a7864219
> Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
>
>