Hi Andrei, what is your use-case for hot-swap? What do you mean by this?
If you want a hotdeployment - yes it's fileinstaller that does the job for the deploy folder if you want to update a bundle that is installed from a maven url for example, just do a update on the bundle Id in the shell and you'll be fine. If you're developing you have the command dev:watch id and it'l update your bundle as soon as it's installation source is updated (e.g. from a maven url) Regards, Achim 2011/11/30 Andrei Pozolotin <[email protected]> > Hello; > > so that I do not re invent the wheel, > I hope there is a write up on the web somewhere, something like: > > "karaf best practices: bundle hot swap" > > to address questions like: > * does file install / deploy work for this? > * how about feature:install? > * should I use external ssh/scp with file install? > * should I use embedded ssh/scp with file install? > * which approach properly handles bundle life cycle, update/refresh? > * which approach properly handles osgi scr bind/unbind & > activate/deactivate? > * how do I test bundle hot swap in karaf properly? > * etc. > > can you please share some pointers? > > Thank you, > > Andrei. > > -- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/>
