Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Date: Fri, 26 Oct 2012 12:57:12 +0000 (UTC)
From: "Philipp Marx (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Message-ID: <203242304.31857.1351256232773.JavaMail.jiratomcat@arcas>
Subject: [jira] [Created] (FELIX-3737) HttpFilter service.ranking is not
 evaluated properly under some circumstances
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Philipp Marx created FELIX-3737:
-----------------------------------

             Summary: HttpFilter service.ranking is not evaluated properly under some circumstances
                 Key: FELIX-3737
                 URL: https://issues.apache.org/jira/browse/FELIX-3737
             Project: Felix
          Issue Type: Bug
          Components: HTTP Service
    Affects Versions: http-2.2.0
            Reporter: Philipp Marx
            Priority: Minor


If a Http-Filter is registered with a service.ranking of Interger.MAX_VALUE and another Http-Filter is registered with a negative service.ranking (like org.apache.sling.i18n.impl.I18NFilter which has -700) the evaluation of the sorting order (mostly) fails.

The problem is FilterHandler's compareTo method which leads to an overflow in this case:

 public int compareTo(FilterHandler other)
 {
     return other.ranking - this.ranking;
 }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira