Hi OSGi is complicated, in fact a lot.
Camel has been supporting osgi for almost all its lifetime. And back then, only spring-dm was available for running camel on servicemix. And then later blueprint came, and they needed to share some code, hence core-osgi and core-xml. And back then the osgi containers was also more buggy and could not work well when you had core-osgi and core-xml as separate bundles. Also split packages problems and other endless problems. And then recently scr came along. Bottom line historical, osgi problems and whatnot makes the world as today. On Sat, Mar 12, 2016 at 6:36 PM, Quinn Stevenson <qu...@pronoia-solutions.com> wrote: > While I was trying to track down another issue, I discovered that the the > dependencies on the classes in camel-core-osgi are handled differently by > camel-blueprint and camel-scr. > > The camel-blueprint bundle includes the class files from camel-core-osgi (and > camel-core-xml for that matter), while camel-scr declares a dependency on the > package and uses the camel-core-osgi bundle. > > Shouldn’t the classes in camel-core-osgi be used the same way? > > -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
