Closed pszuster closed 6 years ago
@pszuster what is the reason for changing the data shape after RHDM-Insurance API call? This can only lead to issues as the data shape will not correspond to response from the API and the mapper will operate under false pretences.
@pszuster what is the reason for changing the data shape after RHDM-Insurance API call? This can only lead to issues as the data shape will not correspond to response from the API and the mapper will operate under false pretences.
@zregvart removing the" DataShape" extension doesn't change the behaviour (it shouldn't be in that reproducer sample). It is there because the combination of adding a script step that converts body to string and that extension makes the integration work.
@pszuster there seems to be an inconsistency between the the error and the integration export you provided. The error contains 7 steps and the integration contains 5 -- I think matching what you reference in steps to reproduce (AMQ -> DataMapper -> API -> DataMapper -> AMQ). This makes it really hard to troubleshoot, can you provide logs from the integration that has the 5 steps you outlined in the steps to reproduce?
I can reproduce this using AMQ (data shape: JSON Instance {"data": "here"}
) -> mapper -> API (TODO API, action: create task) -> mapper -> AMQ (data shape: JSON Instance {"other": "data"}
) on 1.4.x.
I'll try to debug a bit more and find a solution.
I'll try to debug a bit more and find a solution.
I created a workaround that makes it work reproducing-export_workaround.zip
I found the issue with message type conversion when using SJMS (ActiveMQ) connector. In combinations where type conversion is required the integration will fail. One of such cases is handling the response stream form the API connector in the mapper.
I would not call this a blocker, having a script as demonstrated here, will help as it performs type conversion before the mapper.
cc @syndesisio/qe @gaughan @kcbabo @paoloantinori @heiko-braun
@pszuster this should be now fixed on the version in master
, you can test it from master using the quick installation instructions or use a daily build -- this should be included in tomorrow's version: 1.5.4-20180821.
This is a...
The problem
When trying to map an API Connector's output to another datashape with a DataMapper I get the following error in the log:
Export of the integration: amqToRHDMtoAmq-export.zip
Syndesis version: 1.3.12.fuse-000001-redhat-2
Expected behavior
Be able to map an API connector's output to another dataformat.
Screenshot
Request and Response Data
API Endpoints and Schemas
Tasks involved / Steps to Reproduce
1.Create connection to AMQ 2.Create connection to API Insurance Quoting.json.txt