Hi there, I'm with a group that provisions our own instance of Karaf. We've run into an issue that might be a bug, so I wanted to ask here first.
It has to do with a *first-time deployment and start-up* of the Karaf container. We un-tar the instance but before starting it we put our application JARs into the deploy folder. When Karaf starts it appears to have no priority over it's own bundles as a part of the boot features set versus the files in the deploy folder. As a result some of our biundles are installed first (with bundle IDs in the 10s) versus their dependencies that are part of Karaf's boot features (IDs much higher). Our JARs therefore are in an installed state, and when you try to start them they fail saying they are missing dependencies even though the dependencies are listed as active bundles. Contrast this to the same initial distribution unpacked and started with an empty deploy folder. We then take the exact same files from the experiment above and drop them into the deploy folder with Karaf running. This time they start up properly as active having found their dependencies. It seems odd that this should occur. My guess is that when starting up for the first time Karaf should prioritize it's own features and internal bundles over anything in the deploy folder, but that doesn't seem to be the case. Any advice or confirmation or clearing up of misconceptions of how Karaf is supposed to work would be appreciated. Thanks! -Allen -- View this message in context: http://karaf.922171.n3.nabble.com/Hot-deploy-priority-on-first-start-up-tp4047948.html Sent from the Karaf - User mailing list archive at Nabble.com.
