You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Kasun Indrasiri (JIRA)" <ji...@apache.org> on 2011/09/21 10:37:09 UTC
[jira] [Created] (SYNAPSE-801) Synapse changes the message type to
application/xml for all outgoing requests
Synapse changes the message type to application/xml for all outgoing requests
-----------------------------------------------------------------------------
Key: SYNAPSE-801
URL: https://issues.apache.org/jira/browse/SYNAPSE-801
Project: Synapse
Issue Type: Bug
Reporter: Kasun Indrasiri
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] [Assigned] (SYNAPSE-801) Synapse changes the message type to
application/xml for custom content types in the out path
Posted by "Kasun Indrasiri (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kasun Indrasiri reassigned SYNAPSE-801:
---------------------------------------
Assignee: Kasun Indrasiri
> 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
> Assignee: 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] [Updated] (SYNAPSE-801) Synapse changes the message type to
application/xml for custom content types
Posted by "Kasun Indrasiri (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kasun Indrasiri updated SYNAPSE-801:
------------------------------------
Summary: Synapse changes the message type to application/xml for custom content types (was: Synapse changes the message type to application/xml for all outgoing requests)
> Synapse changes the message type to application/xml for custom content types
> ----------------------------------------------------------------------------
>
> Key: SYNAPSE-801
> URL: https://issues.apache.org/jira/browse/SYNAPSE-801
> Project: Synapse
> Issue Type: Bug
> Reporter: Kasun Indrasiri
>
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] [Resolved] (SYNAPSE-801) Synapse changes the message type to
application/xml for custom content types in the out path
Posted by "Kasun Indrasiri (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kasun Indrasiri resolved SYNAPSE-801.
-------------------------------------
Resolution: Fixed
This is fixed on trunk
> 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
> Assignee: 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] [Updated] (SYNAPSE-801) Synapse changes the message type to
application/xml for custom content types in the out path
Posted by "Kasun Indrasiri (JIRA)" <ji...@apache.org>.
[ 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] [Updated] (SYNAPSE-801) Synapse changes the message type to
application/xml for custom content types
Posted by "Kasun Indrasiri (JIRA)" <ji...@apache.org>.
[ 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.
This should be fixed in Axis2FlexibleMEPClient 'processWSDL2RESTRequestMessageType' method and there we need to set the correct message type on axisOutMsgCtx and originalInMsgCtx.
was: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 (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
> -----------------------------------------------------------------------------
>
> 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.
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org