On Tue, Dec 15, 2009 at 13:57, Carsten Ziegeler <[email protected]> wrote: >> 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 :)
So what is the original question about? >> For example, if no resource type could be found (well, the node type >> is always present...), [...] > Hmm, sorry, can you please elaborate a little bit? Usually files or > folders have an nt:folder or nt:file resource type. That's what I meant with "the node type is always present". I actually meant, if no *explicit* resource type, ie. no sling:resourceType, could be found. However, I have no good idea yet, how to actually map that to resources and resource types. ;-) Regards, Alex -- Alexander Klimetschek [email protected]
