We are trying to improve the responsiveness of some bulk message
processes such that a large batch does not flood a queue and prevent
subsequent smaller batches getting through in a timely fashion. For
example, a job to import millions of records from CSV may take an hour
but a smaller job to i
Is there a standard pattern for defining Camel endpoints so that
commonly used endpoint settings do not need to be repeated in every
endpoint definition? For example, every RabbitMQ endpoint I declare
always repeats the same connection settings like the following:
rabbitmq://{{rabbitmq.host}}
on the other hand, many people use the Camel components using
configuration and uris only ... you can use the FTP component
without even have it on the classpath at development time
It didn't occur to me that this was a design goal. It makes sense but I
would never take advantage of it be
Code snippets in the docs at camel.apache.org are not rendering for me.
For example, all of the example endpoint URLs on
https://camel.apache.org/components.html are empty. When I inspect the
page source I can see the script blocks containing the code snippets so
I guess this is a JavaScript issue.
Yeah I posted the same question yesterday. The following Greasemonkey
script fixes the issue for me:
// ==UserScript==
// @nameCamel Code Snippets
// @namespace ncjones
// @include https://camel.apache.org/*
// @version 1
// @grant none
// ==/UserScript==
document.getEleme
