[jira] [Reopened] (CXF-6902) Problem with resource that returns Object with CXF version == 3.1.2
[
https://issues.apache.org/jira/browse/CXF-6902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Balarami Reddy reopened CXF-6902:
-
Hi Sergey,
I debugged the code of 2.7.3 to see how it was working and which provider could
convert integer to JSON and it was found to be PrimitiveTextProvider.
I also observed one change from 2.7.3 to 3.1.2 in PrimitiveTextProvider
supports method.
In 3.1.2, an extra condition is added
mt.isCompatible(MediaType.TEXT_PLAIN_TYPE) which means this provider is
supported only if the method produced type is compatible with TEXT_PLAIN_TYPE
and it broke backward compatibility where it used to work for APPLICATION_JSON
also.
Please advice us on what best can be done.
Thanks
Balaram.
> 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
>Assignee: Sergey Beryozkin
>
> 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)
[jira] [Assigned] (CXF-6912) introduce CONNECTION_MAX_IDLE property for AHC
[ https://issues.apache.org/jira/browse/CXF-6912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-6912: - Assignee: Freeman Fang > introduce CONNECTION_MAX_IDLE property for AHC > -- > > Key: CXF-6912 > URL: https://issues.apache.org/jira/browse/CXF-6912 > Project: CXF > Issue Type: Improvement > Components: Transports >Reporter: Freeman Fang >Assignee: Freeman Fang > > currently we have the CONNECTION_TTL property for AHC, this is used to > specify a connection TimeToLive, no matter the connection is active or not. > For some scenarios, users wanna specify the value for how long an idle > connection should exist in the connection pool, if reach that timespan, just > close the idle connection. > We need introduce another property named CONNECTION_MAX_IDLE to do it. To let > CONNECTION_MAX_IDLE take effect, customer need configure CONNECTION_TTL as > "0" which means the connection does not have an expiry deadline and use the > CONNECTION_MAX_IDLE to close the idle connection only, so that the actively > used connection could be still reused by the connection pool -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CXF-6912) introduce CONNECTION_MAX_IDLE property for AHC
Freeman Fang created CXF-6912: - Summary: introduce CONNECTION_MAX_IDLE property for AHC Key: CXF-6912 URL: https://issues.apache.org/jira/browse/CXF-6912 Project: CXF Issue Type: Improvement Components: Transports Reporter: Freeman Fang currently we have the CONNECTION_TTL property for AHC, this is used to specify a connection TimeToLive, no matter the connection is active or not. For some scenarios, users wanna specify the value for how long an idle connection should exist in the connection pool, if reach that timespan, just close the idle connection. We need introduce another property named CONNECTION_MAX_IDLE to do it. To let CONNECTION_MAX_IDLE take effect, customer need configure CONNECTION_TTL as "0" which means the connection does not have an expiry deadline and use the CONNECTION_MAX_IDLE to close the idle connection only, so that the actively used connection could be still reused by the connection pool -- This message was sent by Atlassian JIRA (v6.3.4#6332)
