[
https://issues.apache.org/jira/browse/CXF-6515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14681491#comment-14681491
]
Sergey Beryozkin commented on CXF-6515:
---------------------------------------
Yeah, good catch :-), but see my earlier comment at
https://issues.apache.org/jira/browse/CXF-6515?focusedCommentId=14655219&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14655219
That particular issue has been fixed, but note that the factory now accepts two
comparators, one for readers, one for writers, because the spec (the spec again
:-)) has slightly different rules for comparing readers and writers and I
thought it was important to let users 'know' which custom comparator sorts
readers and which one sorts writers, though as the test in the commit shows
you can use the same comparator between readers and writers as before.
> provider sorting not right
> --------------------------
>
> Key: CXF-6515
> URL: https://issues.apache.org/jira/browse/CXF-6515
> Project: CXF
> Issue Type: Bug
> Reporter: Romain Manni-Bucau
> Assignee: Sergey Beryozkin
> Fix For: 3.1.3, 3.0.7
>
>
> Didnt dig too much into it but seems sorting with a custom comparator is not
> respected, can be linked to 6514, if this 6514 is fixed I'll test again to
> confirm this one
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
