Hello.
Yes, I mean one of the (>100) bundles that contain the Camel's routes.
The code that must retrieve the version is not in these bundles, but
in a common one that exposes services that are called on events
(EventNotifier). Such external services do not know the name of the
Camel routes
Hi
what do you mean by "your bundle" ? You mean the one containing the route ?
If your bundle just contains the blueprint xml, the most secure way is
to get the bundle list, filter by your name to get the version.
Regards
JB
On Fri, Jul 8, 2022 at 10:45 AM Ephemeris Lappis
wrote:
>
> Hello
Hello again !
I've tested it, but I'm afraid the solution #2 doesn't work as is.
With the following code, the retrieved bundle seems to be the system's
bundle that creates the exchange, not mine :
// e is the current Exchange
final Bundle bundle = FrameworkUtil.getBundle(e.getClass());
return
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
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
wrote:
>
> Hello.
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