>> On Thu, Jul 1, 2010 at 1:52 PM, Ian Boston <i...@tfd.co.uk> wrote:
>>> Hi,
>>> I want to be able to stop the listing of all child nodes at specific urls,
>>> but still allow direct access to items in a subtree.
>>> Any ideas how this is best done in Sling? (and webdav)
>>>
>>> I have lots, but dont know which is going to be best.
>>> eg
>>> Use a ServletFilter to filter all access to /_user
>>> Patch/Configure webdav to only PROPFIND etc /_user/ieb if ieb is the logged
>>> in user.
>>> [...]
> On 1 Jul 2010, at 14:19, Vidar Ramdal wrote:
>> This would be fairly easy to implement using a custom AccessManager.
>> But maybe that is not an option.
On Thu, Jul 1, 2010 at 5:07 PM, Ian Boston <i...@tfd.co.uk> wrote:
> That is a good point,
> however doing it at that level will prevent getting child nodes of a node....
> which is needed to get the burried public resource
>
> /_user/ieb/public/xyz.pdf
>
> to get that the jcr resolver is going to need to effectively do
> session.getNode("/_user").childNodes()
>
> and the AccessManager wont be able to tell if thats for getting xyz.pdf or to
> get the child nodes.
>
> ie, at JCR level all the elements of the path have to be resolvable for the
> target resource to be readable.
Ah, sorry, I misread your original post. So you want to be able to
receive the child resource if you know the address, right?
Then a custom AccessManager won't do. Unless you can deny access to
only the parent node, then I'm pretty sure you won't be able to list
child nodes - but you won't be able to read the parent node either, of
course.
--
Vidar S. Ramdal <vi...@idium.no> - http://www.idium.no
Sommerrogata 13-15, N-0255 Oslo, Norway
+ 47 22 00 84 00 / +47 22 00 84 76
Quando omni flunkus moritatus!
