Ohh yeah, at the beginning the mechanism was quite confusing, it still give me some headaches sometimes, like a feature with no dependencies with a bundle importing only a servlet triggering a refresh of the whole platform.
"For the update, I don't know which karaf version you are using, but Karaf 4.2.x has some improvements with feature:update." We are using karaf 4.1.5 right now, we will wait for Karaf 4.2.1 to start some testing. "Feel free to create Jira corresponding to your ideas, and feel free to contribute. Any help is welcome !" Will do, i plan to release an open-source version of our remote admin for karaf which i am working on my free time, should take a couple months. Thanks! jbonofre wrote > Hi, > > Thanks for sharing your experience. > > I don't say that it's your case, but most of the time, when people > complains about refresh, it's because they don't know/understand the > underlying mechanisms. > Basically, I had the case with a customer that used a bunch of optional > import and complain of the refresh: the issue was basically a design > error and an mistake in the bundles. > > For the update, I don't know which karaf version you are using, but > Karaf 4.2.x has some improvements with feature:update. > > About spring-boot like, it's part of the karaf-boot scope. > > Anyway guys, I think you have very good ideas and it's really great you > share your experience/use cases. Feel free to create Jira corresponding > to your ideas, and feel free to contribute. Any help is welcome ! > > Thanks > Regards > JB > > On 17/08/2018 21:34, Castor wrote: >> I can tell a little about my experience with karaf. >> >> Here we have an ERP writen in delphi (that was written in natural before >> that) which we need to "upgrade" to a cloud capable software, using the >> same >> database and mantaining the old software while we rewrite negotial rules >> in >> java. Great part of our clients are small-medium with on-premises, so we >> had >> to maintain a architecture easy enough for on-premises and able to use a >> cloud structure with clusters and so on. >> >> So, we are using karaf for that, OSGi services lets us to build >> "microservices" and have a easier reuse of Negotial Rules, with common >> transactions and so on (icks for XA . >> >> Well, it works, but we have some headaches, we had to build or own >> dependency mechanism, because every single feature refreshed the hell of >> karaf, we also built an remote admin to update services on-the-fly in >> every >> single customer, it's working quite nicely, we still have some trouble >> with >> failed bundles, but nothing irremediable. >> >> Two things that would help us a lot, a spring-boot like app and an easier >> way to update karaf version, for the updates we had to create a updater >> which saves a list of negotial bundles, reinstall karaf and restores the >> bundles, it works but it's quite meh. >> >> >> >> >> >> >> -- >> Sent from: http://karaf.922171.n3.nabble.com/Karaf-Dev-f930721.html >> > > -- > Jean-Baptiste Onofré > jbonofre@ > http://blog.nanthrax.net > Talend - http://www.talend.com -- Sent from: http://karaf.922171.n3.nabble.com/Karaf-Dev-f930721.html
