I have this in my route:
${type:java.util.Collections.EMPTY_LIST}
Look like it is caused by my:
Which is very strange, since the ones that have default value are not being
filtered.
However my intention (when using the header filter strategy) is to filter
incoming HTTP request headers, not to the headers that are copied from the
query
Hello:
Running Camel 3.0.1. I have a Rest DSL, where Query Params are not being
copied to the Exchange
You should be able to set an HazelcastInstance at component level.
So you can define a Config with all of your parameters call an
Hazelcast.getOrCreateHazelcastInstance(config)
and then set the instance on your component.
Il giorno gio 6 feb 2020 alle ore 19:21 Gershaw, Geoffrey A. <
Hi All,
The samples on the component's webpage do not include where to put the IP
address/port of the hazelcast node? Could someone share how to configure it or
update the webpage?
Thanks
Geoffrey A Gershaw
CREDIT SUISSE SECURITIES (USA) LLC
CS Sec USA LLC | Credit IT Global Loans Dev - RL,
The issue is not a-synchronic interaction between the SEDA producer and the
SEDA consumer, that is fine, I know it is an asynchronous interaction, but the
fact that the steps within the SEDA route are not executed in a synchronous
manner. i.e. setting the synchronous=true property in the
as it is known that SEDA component is asyn component, but direct is sync
one, can you use direct instead of seda?
On Wed, Jan 29, 2020 at 2:42 PM Alex Soto wrote:
> Thanks Claus,
>
> I tested adding synchronous=true to the SEDA consumer, but it does not
> make any difference.
> The only thing
I’m sorry Guillaume, but I don’t see the similarity, although you may know
something I don’t.
In any case do you know of a workaround?, basically I need to be able to enable
tracing of exchange headers (in Blueprint) for troubleshooting, but I have not
yet found how.
Best regards,
Alex soto
I created an issue for this: https://issues.apache.org/jira/browse/CAMEL-14510.
Op 31 jan. 2020, om 17:24 heeft Andrea Cosentino
mailto:anco...@gmail.com>> het volgende geschreven:
Can you open a JIRA issue if you think this is a bug ?
Thank you
Il giorno ven 31 gen 2020 alle ore 17:23 Remco
