Hello
Thanks for your answer.
Your solution #2 should be better since it doesn't imply a modification
of our almost hundred projects.
Does it mean that the Exchange class is always managed in a class loader
that's in the scope of each bundle ?
I'm going to try that and confirm it works in our context.
Thanks again.
Regards.
Ephemeris Lappis
Le 08/07/2022 à 06:49, Jean-Baptiste Onofré a écrit :
Hi,
You have two ways to do that:
1. in your blueprint XML, you can inject blueprintBundleContext
(implicit bean) in your camel route/processor.
2. you can do FrameworkUtil.getBundle(Exchange.class).getBundleContext()
Regards
JB
On Thu, Jul 7, 2022 at 4:33 PM Ephemeris Lappis
<ephemeris.lap...@gmail.com> wrote:
Hello.
I'd like to know if there's some way to retrieve the bundle version
from either the CamelContext or the CamelMessage objects.
The code should be executed in a service that is provided from another
bundle. I suppose I could get the BundleContext using the
FrameworkUtil.getBundleContext(someClass), but I don't know how I
could get the given "someClass" that would match the origin Camel
Exchange scope.
All our Camel contexts are executed from OSGi blueprints packaged as
bundles, and they share the services that need to get the
corresponding bundles versions.
Any idea ?
Thanks for your help.
Regards.
--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel
antivirus Avast.
https://www.avast.com/antivirus
