Hi
We started with implementing this in the route consumers (eg from)
where we have control of the lifecycle of. the exchange and what
happens, so we can ensure
they get released back to the pool
PollingConsumer are used more sparingly and only in the pollEnrich EIP
and then from the
Hi Claus,
would this change polling consumers in a way that the exchange from
the previous step is passed on to the polling consumer? I'm guessing
not, but just in case, I think that would be a welcome change.
Currently for polling consumers in poll enrich scenarios it's
difficult to pass data
Hi
I am putting the final touches on
https://issues.apache.org/jira/browse/CAMEL-16222
https://issues.apache.org/jira/browse/CAMEL-16213
Which is a large commit as it uses a new ExchangeFactory api
that components with consumers now use when they create a Camel Exchange
instance to contain the