Hi Justin
Thank you for the clarification! So, in summary, when /something is resolved
for /something.html, the question is not whether something.html is a child
of /something, but whether .html I an extension of the sibling resource
/something. That's where I got it wrong.
Kind regards,
Olaf
---
Hi,
On Fri, Jan 17, 2014 at 2:56 PM, Justin Edelson
wrote:
> ...You wrote this in your JIRA issue which I think identifies the problem:
>> In essence, a ResourceProvider can not utilize any selectors or extensions
>> to parametrize the resolution of its root resource.
>
> A ResourceProvider shou
Hi Olaf,
Sorry, I don't know how to explain this any better than what I said
earlier in the week. There is no inconsistency.
For a request like /root/child.html, Sling will try *first* for the
full resource path /root/child.html. Since your resource provider is
rooted at /root, it is asked for the
Hello Justin
I believe we have a misunderstanding: You are absolutely right - but I have
no intention to alter the described behavior. What I mean is that the
behavior of the resource resolution using a resolved provider is
inconsistent as it differs between the root path and (potential) child pat
