You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Sameera Jayasoma (JIRA)" <ji...@apache.org> on 2010/10/28 15:14:20 UTC
[jira] Created: (SYNAPSE-703) A bug in setting the MESSAGE_TYPE
property, when there are additional meta information in the Content-type
header
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-703) A bug in setting the MESSAGE_TYPE
property, when there are additional meta information in the Content-type
header
Posted by "Supun Kamburugamuva (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927349#action_12927349 ]
Supun Kamburugamuva commented on SYNAPSE-703:
---------------------------------------------
Applied the patch. Many thanks Sameera for the contribution.
> 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
>
> Attachments: patch-SYNAPSE-703.txt
>
>
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Resolved: (SYNAPSE-703) A bug in setting the MESSAGE_TYPE
property, when there are additional meta information in the Content-type
header
Posted by "Supun Kamburugamuva (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Supun Kamburugamuva resolved SYNAPSE-703.
-----------------------------------------
Resolution: Fixed
> 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
>
> Attachments: patch-SYNAPSE-703.txt
>
>
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-703) A bug in setting the MESSAGE_TYPE
property, when there are additional meta information in the Content-type
header
Posted by "Sameera Jayasoma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sameera Jayasoma updated SYNAPSE-703:
-------------------------------------
Attachment: patch-SYNAPSE-703.txt
Attached a patch. This solves the above issue.
> 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
>
> Attachments: patch-SYNAPSE-703.txt
>
>
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org