[ https://issues.apache.org/activemq/browse/CAMEL-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51590#action_51590 ]
Willem Jiang commented on CAMEL-1589: ------------------------------------- I just found the CamelTransportContants.CONTENT_TYPE is used by the CamelTransport. The integration test of CustomerServicesTest shows the user case. there is no protocol header defined in Camel-xxx component, camel transport need to copy the content-type between the CXF message and Camel message back and forth. Since the DefaultCxfBinding will not be used in CamelTranpsort, I just revert the change of the CXFHeaderHelper, and change to use Camel style header name CamelTransportContants.CAMEL_CONTENT_TYPE = "CamelContentType" http://svn.apache.org/viewvc?rev=772881&view=rev > Clean up the CamelTransportConstants.CONTENT_TYPE > -------------------------------------------------- > > Key: CAMEL-1589 > URL: https://issues.apache.org/activemq/browse/CAMEL-1589 > Project: Apache Camel > Issue Type: Improvement > Affects Versions: 2.0-M1 > Reporter: Willem Jiang > Assignee: Willem Jiang > Fix For: 2.0-M2 > > > Here is the mail thread about it. > http://www.nabble.com/Re%3A-svn-commit%3A-r772054---in--camel-trunk-components-camel-cxf-src%3A--main-java-org-apache-camel-component-cxf-CxfHeaderFilterStrategy.java--test-java-org-apache-camel-component-cxf-CxfRawMessageRouterTest.java-tt23412367.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.