On 10/18/07, Tobias Bocanegra <[EMAIL PROTECTED]> wrote:
> > ....The resolver would set the Resource and SlingRequestPathInfo on the
> > context immediately. ...
> ...this limits the 'resource resolution' to only work with a sling
> request context....
I agree with Toby, and also the
void resolveResource(SlingRequestContext context) throws SlingException;
introduces unnecessary coupling between the ResourceResolver and the
SlingRequestContext
> ...what about a:
>
> interface ResolvedResource extends Resource {
> public String getResolutionPath();
> }...
Good idea, cleaner than my suggestion, I'll do it like that unless
someone objects.
-Bertrand
