On Tue, Jul 3, 2012 at 11:06 AM, Jukka Zitting <[email protected]> wrote: > Hi, > > On Tue, Jul 3, 2012 at 10:55 AM, Bart van der Schans > <[email protected]> wrote: >> We running into a (potential) issue with same name siblings and >> authorization and I would like to have some feedback before we try to >> fix this (if needed at all). > > Your problem boils down to having "same name siblings" and > "authorization" in the same sentence, or perhaps even having same name > siblings in the first place. You're probably better off if you try to > avoid the SNS feature entirely. > >> Which is a bit odd, because how can the session know there is more >> than one item sibling? Does anybody knows what the spec has to say >> about this? > > The spec leaves this open by explicitly allowing access control to > leave gaps in the SNS sequence. It's not an elegant solution, but > AFAIUI nobody really considered such interactions when the SNS feature > was specified (IIUC it came up just as a logical consequence of the > XML import feature).
correct. FWIW, here's what the jcr 2.0 spec says WRT sns and access & control: [0] (22.5) cheers stefan [0] http://www.day.com/specs/jcr/2.0/22_Same-Name_Siblings.html > > BR, > > Jukka Zitting
