cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <>
Subject [jira] [Commented] (CXF-6514) endpoints returning String can't use a custom provider
Date Tue, 04 Aug 2015 12:54:04 GMT


Sergey Beryozkin commented on CXF-6514:

> 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:
>             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

View raw message