You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2021/01/30 08:55:00 UTC
[jira] [Resolved] (CAMEL-16112) Camel REST deserializes response to
wrong type
[ https://issues.apache.org/jira/browse/CAMEL-16112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-16112.
---------------------------------
Fix Version/s: 3.8.0
3.7.2
Resolution: Fixed
Thanks for reporting and the unit test.
> Camel REST deserializes response to wrong type
> ----------------------------------------------
>
> Key: CAMEL-16112
> URL: https://issues.apache.org/jira/browse/CAMEL-16112
> Project: Camel
> Issue Type: Bug
> Affects Versions: 3.7.1
> Reporter: Krzysztof Jamróz
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 3.7.2, 3.8.0
>
> Attachments: RestDataformatTest.java
>
>
> Camel REST component deserializes response to wrong type when the type is configured using {{outType}} parameter. I attached test demonstrating the issue. It runs fine in Camel 3.7.0.
> My observation is that both routes share the same {{DataFormat}} instance which is configured by first route and used by the second one. I think the problem might be not in the REST component itself but due to recent changes in data format cache'ing (CAMEL-16032, CAMEL-16045).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)