Hi,
Am Donnerstag, den 18.10.2007, 16:59 +0200 schrieb Bertrand Delacretaz:
> On 10/18/07, Tobias Bocanegra <[EMAIL PROTECTED]> wrote:
>
> > ...what about a:
> >
> > interface ResolvedResource extends Resource {
> > public String getResolutionPath();
> > }
>
> Even simpler, we weren't really using Resource.getURI until now, so I
> simply changed its comment, and will use it instead:
>
> /** The canonical URI that the ResourceResolver used to load this
> * Resource. As microsling currently access content over JCR only,
> * URIs without a prefix indicate a JCR path in our Repository.
> * Microsling uses "/content/xyz" for this URI instead of
> "jcr:///content/xyz",
> * for example.
> */
> String getURI();
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.
Now, this meaning is overlayed with "the part of the request URI leading
to the resolution of the JCR item". this not always be the same as the
JCR item's path. Hence, I would strongly suggest to not use the getURI
method for this case.
Regards
Felix
>
> -Bertrand
