Hi all,

I have this "conflicting" case of two servlets:

Resource:
/some/path
sling:resourceType "mylib/imagesprite"

Servlet A (intendend servlet):
sling.servlet.paths = [/libs/mylib/imagesprite/GET.servlet]

Servlet B (from a different app):
sling.servlet.extensions = [jpg, jpeg, gif, png]
sling.servlet.resourceTypes = sling/servlet/default
(it also implements the OptingServlet, with accepts() returning true
for the above resource path)

When the URL "/some/path.some.selectors.png" is requested, Servlet B
is chosen, which is not intended. It looks like the extension has
precedence over the explicit resource type in this case.

This feels unintuitive to me. I would think that first servlets for a
specific resource type are searched for and then things like
extension, selector, etc. are taken into account, to find the most
specific one. Is that a bug?

Regards,
Alex

-- 
Alexander Klimetschek
[email protected]

Reply via email to