Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Wed, 1 Apr 2015 10:54:52 +0000 (UTC)
From: "Sergey Beryozkin (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12783533.1426841036000.91235.1427885692968@Atlassian.JIRA>
In-Reply-To: <JIRA.12783533.1426841036000@Atlassian.JIRA>
References: <JIRA.12783533.1426841036000@Atlassian.JIRA>
 <JIRA.12783533.1426841036059@arcas>
Subject: [jira] [Comment Edited] (CXF-6307) Wrong select the message body
 reader
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sergey Beryozkin edited comment on CXF-6307 at 4/1/15 10:54 AM:
----------------------------------------------------------------

It is typed on Boolean, you have a Boolean class parameter in the signature - meaning you have a generic Boolean type.
I've also mentioned that one does not have to provide explicit Consumes(text/plain) in the default provider for the spec requirement to be met, this is an implementation detail, a provider may have a check done in isReadable for example (CXF does not actually restrict it to text/plain only for Boolean - needs to be tuned too).

I'm still investigating...

 
was (Author: sergey_beryozkin):
It is typed on Boolean, you have a Boolean class parameter in the signature - meaning you have a generic Boolean type.
I've also mentioned that one does not have to provide explicit Produces(text/plain) in the default provider for the spec requirement to be met, this is an implementation detail, a provider may have a check done in isReadable for example (CXF does not actually restrict it to text/plain only for Boolean - needs to be tuned too).

I'm still investigating...

 
> Wrong select the message body reader
> ------------------------------------
>
>                 Key: CXF-6307
>                 URL: https://issues.apache.org/jira/browse/CXF-6307
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 3.0.3
>         Environment: Windows
>            Reporter: Neal Hu
>             Fix For: 3.0.5
>
>
> This is a CTS testcase, the resource class is like this:   
>    @POST
>     @Path("boolean")
>     public Boolean postBoolean(Boolean bool) {
>     	if(bool){    		 
>     		throw new WebApplicationException(Status.NOT_ACCEPTABLE);
>     	}
>         return false;
>     }
> The application provided provider is like this:
> public class MyReader implements MessageBodyReader<Boolean> {
>     @Override
>     public boolean isReadable(Class<?> type, Type type1, Annotation[] antns, MediaType mt) {
>     	return type== Boolean.class;
>     }
>     @Override
>     public Boolean readFrom(Class<Boolean> type,
>                              Type type1,
>                              Annotation[] antns,
>                              MediaType mt, MultivaluedMap<String, String> mm,
>                              InputStream in) throws IOException, WebApplicationException {
> 		return Boolean.valueOf("true");        
>     }
> }
> The request
> Content-Type:text/plain
> Accept:text/plain 
> Method:POST
> Body:false
> According to jsr339 section 4.2.4 Standard Entity Providers java.lang.Boolean, java.lang.Character, java.lang.Number Only for text/plain. Corresponding primitive types supported via boxing/unboxing conversion.
> An implementation MUST support application-provided entity providers and MUST use those in preference to its own pre-packaged providers when either could handle the same request. More precisely, step 4 in Section 4.2.1 and step 5 in Section 4.2.2 MUST prefer application-provided over pre-packaged entity providers.
> 4.2.1 Message Body Reader
> 3. Select the set of MessageBodyReader classes that support the media type of the request, see Section
> 4.2.3.
> 4. Iterate through the selected MessageBodyReader classes and, utilizing the isReadable method of
> each, choose a MessageBodyReader provider that supports the desired Java type.
> It says the entity providers should be sorted by media type firstly then(the media type is the same) on Section 4.2.1 and step 5 in Section 4.2.2 MUST prefer application-provided over pre-packaged entity providers. So org.apache.cxf.jaxrs.provider.PrimitiveTextProvider should be selected as its media type MUST be text/plain and the application provider's media type is */*.(x/y>x/*>*/*)
> So at this point the CTS expected response code is 200 instead of 406, the application provided provider should not be chosen.


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