On 10/22/07, Felix Meschberger <[EMAIL PROTECTED]> wrote:

>... I do not think, that this is a good idea, as it mixes concepts. The
> getURI is intended to tell the path of the resource, so for JCR items,
> the getURI should be the item's path (with or without the jcr: scheme as
> a prefix). In the case of non-JCR items, it should really identify the
> resource....

Ok that makes sense. I have created SLING-76 to add a ResourceMetadata
class that will hold information about the part of the path used by
the ResourceResolver.

This is much cleaner and will allow us to store more information
(cacheability etc.) in that ResourceMetadata object later.

-Bertrand

Reply via email to