Hi,

I observed that when some resource is not found. (In my case, browser
was sending request for  favicon.ico), JcrResourceResolver iterates
through all the resource providers, loads resources and then tries to
match sling:alias property.
I have a custom resource provider which has to make a web service call
to build resource. So ends up making unnecessary service calls for
favicon.ico. I do not even know what the original request is
(favicon.ico), because I always get
same path for which the resource provider is registered.   I managed
to add a guard clause somehow, but I do not think its clean.

So a couple of questions.

1. What is difference between resource resolver and resource provider?
Is it recommended to implement custom resource resolver? Any samples?
2. Can sling:alias behavior be turned off?

Thanks,
Unmesh

Reply via email to