You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2009/08/23 09:08:50 UTC

[jira] Commented: (SMXCOMP-615) Servicemix http binding component does not set the content-type header correctly for soap 1.2 to application/soap+xml

    [ https://issues.apache.org/activemq/browse/SMXCOMP-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53720#action_53720 ] 

Jean-Baptiste Onofré commented on SMXCOMP-615:
----------------------------------------------

Could you give some additional information please ?

Is it using the new HTTP endpoints (http:consumer or http:soap-consumer) ?
Is it using the consumer or provider mode (or both) ?
Could you provide a test case (at least a xbean.xml) ?

I think that the issue is on the HttpSoapConsumerMarshaler that doesn't override the content type in the sendOut message but I would like to be sure.

Thanks
Regards
JB

> Servicemix http binding component does not set the content-type header correctly for soap 1.2 to application/soap+xml
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: SMXCOMP-615
>                 URL: https://issues.apache.org/activemq/browse/SMXCOMP-615
>             Project: ServiceMix Components
>          Issue Type: Bug
>          Components: servicemix-http
>    Affects Versions: servicemix-http-2008.01
>            Reporter: Harsh Marwaha
>
> The content type header is not set correctly for Soap 1.2. The header needs to be application/soap+xml
> Axis 2 (not sure about others) generated clients verify this header with the SOAP URI in the envelope and therefore do not work with the http BC.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.