[
https://issues.apache.org/jira/browse/SYNAPSE-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kasun Indrasiri updated SYNAPSE-801:
------------------------------------
Description:
When we get a response form a back-end, the content type get converted to
application/xml in the out path.
reproducing steps:
Send a GET request to a service that sends content with a custom content-type.
This should be fixed in Axis2FlexibleMEPClient
'processWSDL2RESTRequestMessageType' method and there we need to set the
correct message type on axisOutMsgCtx and originalInMsgCtx.
was:
When we get a response form a back-end, the content type get converted to
application/xml in the out path.
This should be fixed in Axis2FlexibleMEPClient
'processWSDL2RESTRequestMessageType' method and there we need to set the
correct message type on axisOutMsgCtx and originalInMsgCtx.
Summary: Synapse changes the message type to application/xml for custom
content types in the out path (was: Synapse changes the message type to
application/xml for custom content types )
> Synapse changes the message type to application/xml for custom content types
> in the out path
> --------------------------------------------------------------------------------------------
>
> Key: SYNAPSE-801
> URL: https://issues.apache.org/jira/browse/SYNAPSE-801
> Project: Synapse
> Issue Type: Bug
> Reporter: Kasun Indrasiri
>
> When we get a response form a back-end, the content type get converted to
> application/xml in the out path.
> reproducing steps:
> Send a GET request to a service that sends content with a custom content-type.
> This should be fixed in Axis2FlexibleMEPClient
> 'processWSDL2RESTRequestMessageType' method and there we need to set the
> correct message type on axisOutMsgCtx and originalInMsgCtx.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
