jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felix Meschberger <fmesc...@gmail.com>
Subject Re: DM Rule #4: Beware of Same Name Siblings.
Date Mon, 09 Jul 2007 06:09:33 GMT

I completely agree with this asset and would even go one step further:
Do not use SNS under any circumstances unless you know exaclty what you
are doing and are prepared for tons of problems. So about the only use
case for SNS I could imagine is actually importing an XML file into a
item hierarchy, which is never individually modified.

This is my very personal opinion based on very bad experience with SNS.


Am Samstag, den 07.07.2007, 13:16 +0200 schrieb David Nuescheler:
> Explanation
> ---
> While Same Name Siblings (SNS) have been introduced into the spec to
> allow compatibility with data structures that are designed for and
> expressed through XML and therefore are extremely valuable to JCR, SNS
> come with a substantial overhead and complexity for the repository.
> Any path into the content repository that contains an SNS in one of
> its path segments becomes much less stable, if an SNS is removed or
> reordered, it has an impact on the paths of all the other SNS and
> their children.
> For import of XML or interaction with existing XML SNS maybe necessary
> and useful but I have never used SNS, and never will in my "green
> field" data models.
> Example:
> ---
> Use
> /content/myblog/posts/what_i_learned_today
> /content/myblog/posts/iphone_shipping
> instead of
> /content/blog[1]/post[1]
> /content/blog[1]/post[2]

View raw message