[
https://issues.apache.org/jira/browse/FELIX-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
J.W. Janssen resolved FELIX-3737.
---------------------------------
Resolution: Fixed
Fixed in rev.1402499, solved a failing JUnit in rev.1512329.
> 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
> Assignee: Felix Meschberger
> Priority: Minor
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> 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
