Hi Jochen, That's one of big change in Karaf 4.4.0: switch to Pax Web 8.x and directly use Pax Web feature.
Good catch ;) Regards JB On Thu, May 19, 2022 at 4:39 PM Jochen Walz <[email protected]> wrote: > > Hi JB, > > Found it: when installing the war feature, the org.apache.aries > spifly.dynamic.bundle is no longer included. After installing this > explicitly, I could at least take that hurdle. > > And after looking up the changed pax-web configuration settings and adapting > org.ops4j.pax.web.cfg, the http service indeed started ;). > > Now I'm facing some other issue, but that looks like being caused by the > Vaadin framework. > > Thanks! > > Regards > Jochen > > > Am 19. Mai 2022 09:57:56 MESZ schrieb "Jean-Baptiste Onofré" > <[email protected]>: >> >> Hi, >> >> Don't you change maven-bundle-plugin to build your bundle ? If it's >> exactly the same bundle (same requirement in the manifest) then it's a >> missing capability in your runtime. >> >> Regards >> JB >> >> On Wed, May 18, 2022 at 11:17 AM Jochen Walz >> <[email protected]> wrote: >>> >>> >>> Hello, >>> >>> When starting my application in Karaf 4.4.0, I receive the error >>> >>> missing requirement [com.helger.commons.ph-commons/10.1.2] osgi.extender; >>> filter:="(osgi.extender=osgi.serviceloader.registrar)" >>> >>> for a 3rd party library (part of the Vaadin UI framework version 22). With >>> 4.3.6, it works. I couldn't see any difference in the service loader >>> mediator spec between OSGi 7 and 8. >>> >>> Any idea how I could solve that? >>> >>> Thanks and regards >>> Jochen
