Am Donnerstag, den 18.10.2007, 13:56 +0200 schrieb Tobias Bocanegra:
> > public interface ResourceResolver {
> > void resolveResource(SlingRequestContext context) throws
> > SlingException;
> > }
> >
> > The resolver would set the Resource and SlingRequestPathInfo on the
> > context immediately. And I think, the SlingRequestContext probably needs
> > a "backlink" to the request it belongs to, which would also help making
> > the RequestParameterMap generation lazy.
>
> this limits the 'resource resolution' to only work with a sling
> request context. what if i want to resolve a resourse without context
> ? e.g. when i want to check if a respective resource exists?
> i would have to create a fake request context ?
Well, you always have the SlingRequestContext if you have the
HttpServletRequest as the former is a request attribute of the latter.
> what about a:
>
> interface ResolvedResource extends Resource {
> public String getResolutionPath();
> }
Sounds good. Or even add the getResolutionPath to the Resource ?
Regards
Felix
