Hi, Am 11.11.2012 um 14:26 schrieb bokie:
> Hi, > > When I deploy the osgi.cmpn-4.3.1.jar file as apposed to osgi.cmpn-4.2.0.jar Is there a reason for deploying this ? > file I get the following exception: > org.apache.felix.dm.impl.dependencies.ConfigurationDependencyImpl cannot be > cast to org.osgi.service.cm.ManagedService It looks very much there is a duplicate export of the Configuration Admin API at two different versions, one from the osgi.cmpn bundle and one from the Configuration Admin bundle. These do not seem to be the same (you might consider updating the Configuration Admin bundle) and thus the Configuration Admin service wires to its own export (because it looks to be an older version not implementing the newer version exported by the 4.3.1 osgi.cmpn bundle). The Dependency Manager bundle wires to the newer API and thus these two are not compatible. Still this exception looks strange. > > Can someone provide some input on this? See above. > Should I even be trying to deploy the 4.3.1 version of the cmpn with felix > 4.0.3? Good question. The Felix implementations of the OSGi specs usually include the respective API and thus the deployment of the osgi.cmpn bundle is not required and (as in your case) may even cause trouble. Regards Felix > > Thanks, > Bokie > > > > > -- > View this message in context: > http://apache-felix.18485.n6.nabble.com/DependencyManager-osgi-cmpn-4-3-1-tp5000342.html > Sent from the Apache Felix - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
