[
https://issues.apache.org/jira/browse/CXF-6377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14521150#comment-14521150
]
Sergey Beryozkin commented on CXF-6377:
---------------------------------------
The problem with some of TCK tests is that they basically mechanically test
some of spec sentences and by doing so they enforce the runtime to do the bad
HTTP, i.e, send a Content-Type which is supposed to describe the body content
which is not there at all. So on the wire you'd see:
Content-Type: foo/bar
Content-Length: 0
<no content here>
This is a bad practice. The fact that it is enforced via TCK makes me unhappy
at all
> Wrong media type of response
> ----------------------------
>
> Key: CXF-6377
> URL: https://issues.apache.org/jira/browse/CXF-6377
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
> Affects Versions: 3.0.3
> Environment: Windows
> Reporter: Neal Hu
> Fix For: 3.0.5
>
>
> Resource class
> public Response getMediaType() {
> MediaType media = MediaType.APPLICATION_ATOM_XML_TYPE;
> Response response = Response.ok().type(media).build();
> return response;
> }
> get media type from response on client side is null.
> Spec 3.8 Determining the MediaType of Responses
> 1. If the method returns an instance of Response whose metadata includes the
> response media type
> (Mspecified) then set Mselected = Mspecified, finish.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
