Am 23.02.2012 um 12:33 schrieb Michael Dürig: > Having node.type.management.orderable.child.nodes.supported = false > might be a bit harsh. But orderable child node lists and large number of > child nodes are definitely in each other's way. I think we should come > up with a way to let users choose.
Users can already chose: using the node type parameter "orderable". A repository-global decision to use either or does not really help, as in most cases you will have the need for both cases (huge unordered bunch + smaller ordered list). Cheers, Alex -- Alexander Klimetschek Developer // Adobe (Day) // Berlin - Basel
