To make it simple to use, if the options provided, the used in URL. If not,
then you can use it in headers
Sent from Weiquan
> On Nov 16, 2019, at 6:59 AM, Claus Ibsen wrote:
>
> Hi
>
> No you cannot set component or endpoint options as headers. Only a
> limited number of headers can
Hi
No you cannot set component or endpoint options as headers. Only a
limited number of headers can control the endpoints, and they are
documented in the components that support this.
Once aspect which we don't have but which would have been great, was
that these headers was also marked up with
For some component, I could set key and value at the exchange's in or out's
header instead of
using the component's option at the endpoint .
For me, it is not very clearly documented, which options could be set at
in/out /header
set option at endpoint URI
from(xxx)
:
>
> I have two questions regarding Component options:
>
> 1) Is it possible to get all options as a Map
>
> From the context it's possible to get component:
>
> context.getComponent("componentName");
>
> It also possible
I have two questions regarding Component options:
1) Is it possible to get all options as a Map
>From the context it's possible to get component:
context.getComponent("componentName");
It also possible to get the Component documentation like
context.getComponent
Hi,
I am not sure whether I understand your question correctly.
https://example.com/v1/hello?apiKey=a=false will
set the throwExceptionOnFailure endpoint option to false (and forward the
apiKey parameter to the server). Component options are set on the component
level and apply to all
If my endpoint is "https://example.com/v1/hello?apiKey=a;, How do i add
ahc component options (e.g., throwExceptionOnFailure) ?
https://example.com/v1/hello?apiKey=a=false ?
How would ahc differentiate the actual endpoint vs component options ?
--
View this message in context:
Reading Camel Kafka component documentation below:
http://camel.apache.org/kafka.html
What does consumerStreams mean/does in options? Sadly there is absolutely not
documentation or further explanation on this.
Thanks,
Adrian
This e-mail and its contents (to include attachments) are the