Hi, I would drop it with migration path. Example:
" Converting old repositories or xml with same name siblings will convert the composed name to literal names, that means: two nodes 'test' are converted to 'test[1]' and 'test[2]'; removing 'test[1] will not rename 'test[2]' to 'test[1]'. " Regards, Thomas On Feb 8, 2008 4:23 PM, Jukka Zitting <[EMAIL PROTECTED]> wrote: > Hi, > > Support for same name siblings is troublesome and currently the best > practice is to avoid them if possible. In many cases the default > response when we see people having problems with SNS is to tell them > not to use the feature. > > I think that's lame. We should either treat SNS as a first-class > feature that we just haven't been able to make work yet, or explicitly > deprecate it and plan to drop or at least seriously limit the feature > as far as is permitted by the JCR standard. > > The current status where SNS is kind of supported but "you should not > use it!" is IMHO not sustainable in the long run. > > WDYT, is SNS worth the effort, or should we consider dropping it? > > BR, > > Jukka Zitting >
