[ https://issues.apache.org/jira/browse/SLING-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510658#comment-14510658 ]
Felix Meschberger edited comment on SLING-4655 at 4/24/15 8:58 AM: ------------------------------------------------------------------- Fixed in Rev. 1675803: * Added method to create servie registration properties for ServletResourceProvider registration * Added test case for new method was (Author: fmeschbe): Fixed in Rev. 1675803: * Added method to create servie registration properties for ServletResourceProvider registration * Added test case for new method > Servlet Resolver does not use registered servlet's service.ranking property > --------------------------------------------------------------------------- > > Key: SLING-4655 > URL: https://issues.apache.org/jira/browse/SLING-4655 > Project: Sling > Issue Type: Bug > Components: Servlets > Affects Versions: Servlets Resolver 2.3.6 > Reporter: Felix Meschberger > Assignee: Felix Meschberger > Fix For: Servlets Resolver 2.3.8 > > > The Servlet Resolver registers a ResourceProvider for each Servlet service > registered and handled by the ServletResolver, that is, those with a Sling > servlet registration property. > As the ResourceResolver supports ranking of ResourceProviders with the same > root path, the ServletResolver should really register ResourceProvider > services for servlets including the servlet service's service ranking > property, if available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)