Emmanuel Ligne wrote: > > Hi David > > Thx for the reply. > The multi-bundle distro as described needs a manual fixing of the > conf.properties of the Felix distro, what > I cannot do in my environment: my env is automatically built by maven, > based on dependencies. Even felix is installed as a runtime dependency. >
This is a typical 'single class loader' build which delegates dependencies responsibility to a top level pom, which , in the case of an OSGi applicatin , has to be reevaluated, reflecting the fact that a bundle can shared/reused by others components. > My problem is that I cannot modify the felix configuration file, as felix > is seen as a simple "dependency" and installed as a jar by maven > You should depend on API only, not a specific implementation. > -> the manual fixing of the conf.properties of the felix is not > acceptable. > ok > -> so I started to try the singlebundle, but no lock with it due to the > fact that it says it depends on the things it already integrates. > Yes. It appears that your application has a foundation set of bundles which, once loaded, could be shared/used by oothers. > Is there a way to generate a singlebundle-like version of DOSGI that would > not say so ? OTW my comprehension is that this *should* be packaged this > way, as the singlebundle obvious does *not* depend on the jars it already > includes. Right ? > I dont think so. OSGi framework is , by essence modular, not singlebundled... OTH Pierre ----- -- Pierre -- View this message in context: http://cxf.547215.n5.nabble.com/DOSGi-singlebundle-jar-exposing-dependencies-tp3413919p3416222.html Sent from the cxf-user mailing list archive at Nabble.com.
