A bug in setting the MESSAGE_TYPE property, when there are additional meta
information in the Content-type header
-----------------------------------------------------------------------------------------------------------------
Key: SYNAPSE-703
URL: https://issues.apache.org/jira/browse/SYNAPSE-703
Project: Synapse
Issue Type: Bug
Components: Core
Affects Versions: 2.1
Reporter: Sameera Jayasoma
Fix For: 2.1
In the Axis2FlexibleMEPClient class, we set the property
"org.apache.axis2.Constants.Configuration.MESSAGE_TYPE" in the Axis2 Out
MessageContext inside the processWSDL2RESTRequestMessageType() method. The
value of this property is equal to the Content-type of the incoming rest
request. But certain Content-type headers carry addition metadata.
e.g.
multipart/form-data;
boundary=---------------------------146792425113394072101987391937
The solution is to extract the content type from the above string, and set it
as the value of the MESSAGE_TYPE property.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
