Closed vanjikumaran closed 1 month ago
Explanation of the current flow: In the given API, at the end of XML PayloadFactory we are adding "application/xml" as message-type and content-type headers. In enrich mediator, we are not doing such header changes. So the final header is "application/xml" and result is responded as XML.
However, there is a need for identifying the payload that is been loaded back into the message context.
Is this been addressed or fixed?
Description: JSON Payload Reloaded via Enrich Mediator not as JSON format
Suggested Labels:
Suggested Assignees:
Affected Product Version: EI 6.6.0 OS, DB, other environment details and versions:
ProductName: Mac OS X ProductVersion: 10.15.4 BuildVersion: 19E287
openjdk version "11.0.6" 2020-01-14 OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.6+10) OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.6+10, mixed mode)
Steps to reproduce:
Request
Logs
[2020-05-04 10:06:04,411] INFO {org.apache.synapse.mediators.builtin.LogMediator} - To: /laslo/great, MessageID: urn:uuid:57338598-52fa-4f03-accc-0b5422e15af3, Direction: request, bla = {"customerID":"1","shipTo":"LK","purchaseProducts":[{"productId":"1","qty":"16.55"},{"productId":"2","qty":"122.55"},{"productId":"3","qty":"3.55"}]} [2020-05-04 10:06:04,607] INFO {org.apache.synapse.mediators.builtin.LogMediator} - To: /laslo/great, MessageID: urn:uuid:57338598-52fa-4f03-accc-0b5422e15af3, Direction: request, a = =========================, Envelope: <?xml version='1.0' encoding='utf-8'?>sadfa</soapenv:Body></soapenv:Envelope>
Response
Related Issues: