[
https://issues.apache.org/jira/browse/CXF-6902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15290854#comment-15290854
]
Sergey Beryozkin commented on CXF-6902:
---------------------------------------
Actually, I wonder if you really have a JSON representation on the wire,
appears to me in 2.7 you had a default provider converting this Integer to
String. In 2.7 this provider was called PrimitiveTextProvider and it was
supporting all Numbers and String. In CXF 3.1.x, it was split into two, and the
provider which supports Numbers is only effective if "text/plain" Media Type is
produced - it was a TCK-related fix.
> Problem with resource that returns Object with CXF version == 3.1.2
> -------------------------------------------------------------------
>
> Key: CXF-6902
> URL: https://issues.apache.org/jira/browse/CXF-6902
> Project: CXF
> Issue Type: Bug
> Components: JAXB Databinding
> Affects Versions: 3.1.2
> Reporter: Balarami Reddy
>
> Hello,
> We have recently migrated from 2.7 to 3.1.2 and we see a behaviour change in
> CXF which blocked us from making progress.
> The sample code below gives "No message body writer has been found for
> response class Integer" which used to work perfect in CXF 2.7
> This is just sample code only. We have in our product several rest calls
> which return integer/long/Object etc based on some calculations.
> @GET
> @Produces(MediaType.APPLICATION_JSON)
> @Path("/getinteger")
> public Response getInteger() {
> return Response.ok(4).build();
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
