Hello,
Over the last 15 months, we have been successfully operating one of our
platforms using Camel 2.9.1/2.10.1. Recently, we have upgraded each of our
processes to use Camel 2.12.2, and in the main, this has been a very
straightforward process.
Unfortunately, we have observed some unexpected
Willem.Jiang wrote
> Hi,
>
> You can find more information about the change in this JIRA[1]
> [1]https://issues.apache.org/jira/browse/CAMEL-6000
Hi Willem,
Many thanks for your reply. I've reviewed the ticket and sort-of understand
the intent of the change.
However, it doesn't make sense to
Hi Willem,
Many thanks for your reply - apologies for the delay of this response.
Unfortunately, Camel appears to throw an error on startup if the collection
is missing, hence setting it to a dummy value.
As we were using the "dynamicity" flag for reuse of routes, given that we
know the target c
Hello,
We have been undertaking an upgrade from Camel 2.9.1 to Camel 2.12.2, and in
most cases, the upgrade has been very smooth.
Unfortunately, we have spotted a change of behaviour between 2.9.1 and
2.12.2, with respect to the HTTP4 component. Following a upgrade, we are
unable to download con
Hi Claus,
Many thanks - much appreciated. For now, we've left our "downloader"
processes on Camel 2.9.1, so will be interested in a fix, when available.
Best regards, Madhu.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-2-12-HTTP4-Now-seeing-port-number-added-to-Ho
