Hello.
We have about 100 Camel projects relying all on the same pattern,
using the same OSGi services or beans, events listeners, and so on. We
plan to migrate all these projects from an old RH Fuse version to a
more recent Apache Karaf.
I'd like to refactor these projects removing all the duplic
As an idea. We use templating engines (think of Freemarker, Mustache or
Velocity) to generate the blueprint.xml. Then it's possible to have one
base blueprint and based on rules add the beans and context.
Raymond
On Thu, Jun 16, 2022 at 9:30 AM Ephemeris Lappis
wrote:
> Hello.
>
> We have about
Hello,
I am also trying to use global exception configuration in a Camel route that is
built from a template. The template is created ok and the route created from it
is also ok & working. But the global exception handling is not working as
expected.
Maybe there is another way to customize the
Hello,
btw... I'm using Camel 3.13.0 for this work.
...jvh003
Hello.
Thanks for your idea.
I'm afraid it's not going to help me much : our existing blueprints
already come with the common declarations for global services, usual
beans, and specific ones. Indeed we could imagine some kind of script to
clean up them, but we also need a way to replace dupli
