[
https://issues.apache.org/jira/browse/CXF-6515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680191#comment-14680191
]
Romain Manni-Bucau commented on CXF-6515:
-----------------------------------------
Hi Sergey,
here is was the rational behind doing it: replacing jsonprovider and ensuring
jsrprovider is everywhere - clientbuilder and server side, of course client
side was the main motivation.
That said I really understand the spec issue but this sorting issue is just
breaking most of the apps I have and comparator didnt seem to help.
I'll hack up something for know providers (ie get rid of ) JohnzonProvider if
ConfigurableJohnzonProvider is used for instance but there should really be a
way to be more deterministic.
Thinking to spring case I can't imagine a user defining an array/list of
provider and getting something fully different.
Finally from a performance point of view you now iterate over > 6 providers
before getting the most common one where before it was 1.
> 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)
