[
https://issues.apache.org/activemq/browse/SMX4-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Reynaerts closed SMX4-12.
-----------------------------
Resolution: Fixed
Sorry, should be solved in the previous version of servicemix
> Preserving or configuring content-type of http-header
> -----------------------------------------------------
>
> Key: SMX4-12
> URL: https://issues.apache.org/activemq/browse/SMX4-12
> Project: ServiceMix 4
> Issue Type: Bug
> Reporter: Jan Reynaerts
> Assignee: Thomas Termin
>
> I have a servicemix configuration with 3 components:
> - a http-consumer component
> - a http-provider component
> - a jsr-181 component. In the jsr181 component I use a proxy, that exposes a
> wsdl (generated by XFire)
> Messages are sent from the http-consumer component through the jsr-181
> component to the http-provider component. I want to preserve the content-type
> from the incoming message. To do this I use the parameters
> wantHeadersFromHttpIntoExchange and
> wantContentTypeHeaderFromExchangeIntoHttpRequest. However in the
> jsr181-component the content-type gets lost. Is it possible to preserve the
> content-type of a message during his route through servicemix?
> As a work-around (patch) we changed the code of the http-provider in such a
> way, that when the parameter wantContentTypeHeaderFromExchangeIntoHttpRequest
> is true, the content-type is set hardcodedly to the value, that we need .
> Another wish is to make the http-provider -component configurable by
> introducing a new parameter fi "SetContentType". If this parameter isn't
> present, the http-component works in the old way, so nothing changes for the
> existing http-components. And it will only be a fix for those http-components
> that use this new parameter
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
