Alexander Klimetschek wrote: > On Mon, Dec 14, 2009 at 14:51, Carsten Ziegeler <[email protected]> wrote: >>> One might use a rule like "starts with /myapp" >>> but others might use "has a parent node with sling:resourceType sling/album" >>> >> Hmm, do I you mean if I use the jcr resource provider I, the logic >> should be part of the jcr resource provider and if I'm using the file >> provider I should be able to add some logic there? > > I think one should not open up resource providers (that are based on > JCR) to use any kind of programmatic rules. The rules should be simple > and easily "visible" from looking at the repository. Hence, looking at > the path and the resource types along it should be enough. > We already have this mechanism for jcr resources. A pluggable service can be implemented to return any resource type :)
> For example, if no resource type could be found (well, the node type > is always present...), the parent path could be looked at. And you end > up with something like "child/descendent of an sling/album resource" > as resource type. That should IMO work well for your and many other > scenarios. Hmm, sorry, can you please elaborate a little bit? Usually files or folders have an nt:folder or nt:file resource type. Carsten -- Carsten Ziegeler [email protected]
