> Because references a) don't scale at the moment with Jackrabbit Is this a core design constraint or intended to be improved in future Jackrabbit releases?.
> and b) hard references make your content very unflexible regarding partial > copying etc. As Bertrand explains it in his post [1]: > > <snip> > We don't use JCR references, but simply store paths in properties, as > this gives us more flexibility when restructuring things. It's hard to > say what will happen to those tags, and to the very concept of > tagging, over the expected lifetime of our product, so we accept > potentially dangling references (and cope with them at the application > level) to gain content agility. > </snip> > > See also rule 5 of David's model [2]. Right, but if tags are deleted or their names modified you´re forced to search the path tag properties over all the repository and fix the affected nodes. It seems an important drawback. WDYT? > [1] http://dev.day.com/microsling/content/blogs/main/cq5tags.html > [2] http://wiki.apache.org/jackrabbit/DavidsModel
