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 duplicated services
references declarations by a common and more dynamic way of providing
them, with the possibility for adding new ones without updating the
projects themselves. That's why I was thinking about a custom camel
context whose registry should be managed by an external bundle that
binds common services...
Thanks again.
Regards.
Ephemeris Lappis
Le 16/06/2022 à 11:04, ski n a écrit :
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 <ephemeris.lap...@gmail.com>
wrote:
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 duplicated
declarations in the blueprints, and I'm looking for solutions to move
all the services and beans declarations to a single common point of
our code.
What should be the better way to do that ? Is it possible to set a
custom factory for the CamelContext in our blueprints, and use it to
provide "ready to use" contexts with services and beans already set on
the registry ?
Thanks in advance for your ideas.
Regards.
--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel
antivirus Avast.
https://www.avast.com/antivirus
