I have a jar embedded in a bundle that needs to fetch a resource packaged with it like so:
MyBundle
-\\ src
-\\lib
-\\MyEmbeddedJar
-\\src
I Assume that SomeClass
is inside the embedded jar (say, somejar.jar
), and someResource.xml
is in the outer jar, in a lib
directory.
In this case, there is no way to get to that in a non-OSGi context. Let's look at both situations in isolation.
Your someResource.xml
should very well be reachable using the regular (non-OSGi specific) resource loading mechanisms, provided that it is reachable from the Bundle-ClassPath
. For instance, if you have the following manifest header,
Bundle-ClassPath: ., somejar.jar
you will be able to get to your resource using "lib/someResource.xml"
.
Notice the dot on the classpath: this means you can reach classes and resources from the root of the jar. If you forget that, you will only be able to get to classes and resources inside somejar.jar
.
If you're not using OSGi, there is no (reasonably simple) way to get to classes and resources inside of the inner jar that I know of.
Depending on what you want your bundle to look like, you have two options now.
SomeClass
is in an embedded jar? If so, you're at a loss, and you jar will only work using OSGi.somejar.jar
into your jar, you subvert the problem, and your jar can work in both situations.Personally, I'd pick option 2.: unless you have resources that might overwrite each other when you 'merge' the jars, it is no problem at all to have a slight mess of resources inside your bundle.