On 2017-08-07 03:39, Clay Ferguson wrote:
Two thoughts:

1) It's a known issue (severe weakness) in the design of Jackrabbit/Oak
that it chokes like a dog on large numbers of child nodes all under the
same node. Many users have struggled with this, and imo it has been one of
the massive flaws that has kept the JCR from really taking off. I mean,
probably still only 1% of developers have ever heard of the JCR.

Jackrabbit yes, Oak no.

Oak has been designed to handle bigger flat collections, but it does require a container node type that doesn't need to maintain the collection ordering.

Best regards, Julian

Reply via email to