Hi, without actually knowing your application if you have the spring-dm feature and your own features in the same startlevel this is the reason, the spring-extender needs to be started before any spring-related bundles are installed. That's also the reason for the deploy-folder issue you have. The fileInstaller starts very early and therefore bundles started through the fileinstaller sometimes miss dependencies provided later on through features.
After a restart of the container, without cleaning the data directory those issues shouldn't happen anymore. regards, Achim 2012/10/19 kva <[email protected]>: > Hi, > > I am running karaf 2.2.5. I still have some bundles that use Spring DM and > rely on spring-dm feature to fully deploy. I have added the spring-dm > feature to featuresBoot as well as my own bundles. It looks like the > extender is too late to actually notice that my bundles are DM bundles > (Spring column in console is empty). I have the same problem when I deploy > my bundles as part of a .kar. If I drop the .kar file in deploy after > starting up then the bundles deploy fine. > > Is this because both spring-dm and my bundles start at the same start-level? > Or is there another cause? > > Thanks > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Spring-DM-bundles-not-fully-deployed-tp4026486.html > Sent from the Karaf - User mailing list archive at Nabble.com. -- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project Lead blog <http://notizblog.nierbeck.de/>
