[
https://issues.apache.org/activemq/browse/CAMEL-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Balázs Zsoldos updated CAMEL-1018:
----------------------------------
Description:
Imagine a use case when the target systems, where http messages have to be sent
to, are maintained in a database. In that case the http uri is cannot be set in
the camelcontext but it should come from the header of the message.
So the http client should check first if there is an uri in the header and if
not than use the one given in the camelcontext (like for querystring).
was:Imagine a use case when the target systems, where http messages have to
be sent to, are maintained in a database. In that case the http uri is cannot
be set in the camelcontext but it should come from the header of the message.
> camel http Uri from the message header
> --------------------------------------
>
> Key: CAMEL-1018
> URL: https://issues.apache.org/activemq/browse/CAMEL-1018
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-http
> Affects Versions: 1.4.0
> Reporter: Balázs Zsoldos
> Attachments: HttpProducer.patch
>
>
> Imagine a use case when the target systems, where http messages have to be
> sent to, are maintained in a database. In that case the http uri is cannot be
> set in the camelcontext but it should come from the header of the message.
> So the http client should check first if there is an uri in the header and if
> not than use the one given in the camelcontext (like for querystring).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
