[ 
https://issues.apache.org/jira/browse/CXF-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653572#comment-14653572
 ] 

Sergey Beryozkin edited comment on CXF-6514 at 8/4/15 12:55 PM:
----------------------------------------------------------------

> I get the logic but dont see how it can match a real case ie exact produce 
> type should win over java type no?

We do not have to disagree about it - I've had my share of long arguments on 
the spec list about the selection process, ex, I think the custom provider 
should always win, but well, the spec has been written differently. Example, if 
we have a wildcard media type provider with Book class and text/xml provider 
for Object, then one possible view is that surely a Book provider knows better 
how to deal with it - I guess this is what affected the spec text...

> Anyway do you care treating this case in the cxf doc/site please?

This is not a CXF exception of some sort, CXF is now completely compliant. Yes, 
should've updated the docs to let people know, will do



was (Author: sergey_beryozkin):
> I get the logic but dont see how it can match a real case ie exact produce 
> type should win over java type no?

We do not have to disagree about it - I've had my share of long arguments on 
the spec list about the selection process, ex, I think the custom provider 
should always win, but well, the spec has been written differently. 

> Anyway do you care treating this case in the cxf doc/site please?

This is not a CXF exception of some sort, CXF is now completely compliant. Yes, 
should've updated the docs to let people know, will do


> endpoints returning String can't use a custom provider
> ------------------------------------------------------
>
>                 Key: CXF-6514
>                 URL: https://issues.apache.org/jira/browse/CXF-6514
>             Project: CXF
>          Issue Type: Bug
>            Reporter: Romain Manni-Bucau
>            Assignee: Sergey Beryozkin
>
> Seems sorting of providers in ServerProviderFactory is done in a way you cant 
> override the provider used for String type even using a custom @Produces type 
> cause StringTextProvider si always selected.



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

Reply via email to