You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@felix.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/02/02 14:49:34 UTC

[jira] [Resolved] (FELIX-4778) Implement ordering of ServletContextHelper

     [ https://issues.apache.org/jira/browse/FELIX-4778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved FELIX-4778.
-------------------------------------
    Resolution: Fixed

Implemented by separating the registries per SCH and first doing an SCH check

> Implement ordering of ServletContextHelper
> ------------------------------------------
>
>                 Key: FELIX-4778
>                 URL: https://issues.apache.org/jira/browse/FELIX-4778
>             Project: Felix
>          Issue Type: Sub-task
>          Components: HTTP Service
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: http-next
>
>
> Right now, the prefix and ranking of a ServletContextHelper is not correctly considered for request processing. 
> If a request is received, the ServletContextHelper with the longest matchin prefix should process the request first. If there is more than one SCH with the same prefix, they are processed based on their ServiceReference ordering (highest ranking first).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)