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 2010/06/07 11:09:51 UTC
[jira] Created: (SMXCOMP-754) The HttpSoapProviderMarshaler doesn't
set the Content-Type header
The HttpSoapProviderMarshaler doesn't set the Content-Type header
-----------------------------------------------------------------
Key: SMXCOMP-754
URL: https://issues.apache.org/activemq/browse/SMXCOMP-754
Project: ServiceMix Components
Issue Type: Bug
Components: servicemix-http
Affects Versions: servicemix-http-2010.01, servicemix-http-2009.02, servicemix-http-2009.01, servicemix-http-2008.01
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
Fix For: servicemix-http-2010.02
The HttpSoapProviderMarshaler doesn't define Content-Type header (depending of the WSDL).
The fix has been made on the HttpSoapConsumerMarshaler but not on the provider one.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SMXCOMP-754) The HttpSoapProviderMarshaler
doesn't set the Content-Type header
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré resolved SMXCOMP-754.
------------------------------------------
Resolution: Fixed
Revision 952178.
> The HttpSoapProviderMarshaler doesn't set the Content-Type header
> -----------------------------------------------------------------
>
> Key: SMXCOMP-754
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-754
> Project: ServiceMix Components
> Issue Type: Bug
> Components: servicemix-http
> Affects Versions: servicemix-http-2008.01, servicemix-http-2009.01, servicemix-http-2009.02, servicemix-http-2010.01
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: servicemix-http-2010.02
>
>
> The HttpSoapProviderMarshaler doesn't define Content-Type header (depending of the WSDL).
> The fix has been made on the HttpSoapConsumerMarshaler but not on the provider one.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.