Home/ Questions/Q 8622929
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-12T07:09:58+00:00

I have an OSGi bundle (deployed into Karaf 2.2.4) that starts a Camel (2.10.0)

  • 0

I have an OSGi bundle (deployed into Karaf 2.2.4) that starts a Camel (2.10.0) context. The Camel context’s routebuilder has some xquery endpoint URIs such as

"xquery:classpath:Dir1/Dir2/example.xq"

When the context tried to resolve that URI, it failed since the Camel bundle is not in the same classpath as where the .xq file resides. So, I created a url expand function that turns 

"xquery:classpath:..."

into

"xquery:bundle://42.0:6/..."

since I had dealt with bundle URIs and the OsgiBundleResourcePatternResolver earlier in my project when dealing with a ClassPathScanningCandidateComponentProvider (Spring 3.1.1). Unfortunately, I can’t seem to find a way to make Camel’s XQueryComponent use my OsgiBundleResourcePatternResolver.

  1. Am I going about this the right way? Is there an easier way to do this?
  2. If I am, how can I make sure the XQueryComponent can understand a bundle: URI?
  3. Also, is it possible for me to make sure any camel component can understand a bundle: URI?
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Thanks to Claus’ answer, I was able to realize that my .xq file was not in the right directory in its .jar.

    Dir1 resided in root of its .jar file. While running the application in a non-OSGi web container worked fine, Karaf appears to be more strict regarding where resources should be in my .war file. I moved the .xq files to WEB-INF/classes/Dir1/... and now am no longer receiving FileNotFoundExceptions when the code uses xquery:classpath:Dir1/Dir2/example.xq

    • 0