Sometimes it's as simple as adding manifest headers to make the jar game enjoyable in the OSGi sandbox. Sometimes banks / libraries do "naughty" things in the context of OSGi. The golden rule is to not use "Class.forName ()" because OSGi uses class loaders, otherwise it works fine in a single class loader environment. I pulled down the source in SnakeYaml and they are loader based beans using Class.forName.
, CustomClassLoaderConstructor, , , Yaml. . , Yaml, , - , , . , , OSGi.
. .