Hi

Thanks, let me take a look.

Regards
JB

On Fri, Nov 13, 2026 at 6:56 PM apache-karaf-dev.pyr3x.com via dev
<[email protected]> wrote:
>
> Hi JB,
>
> I think this is probably good for now...
>
> https://github.com/apache/karaf/pull/3088
>
> Though I think it makes sense to make a
> assemblies/features/osgitech-jakarta-rs-whiteboard let me know if you
> think it should be refactored that way or is good now.
>
> Though I think it probably makes sense to bring it
>
> On Fri, Nov 13, 2026 at 06:36:24AM +0100, Jean-Baptiste Onofré wrote:
> > Hi guys,
> >
> > Let's include this for 4.5.0. I'm unstacking a bunch of PRs right now, so
> > ready to work/review any PR :)
> >
> > Regards
> > JB
> >
> > On Thu, Nov 12, 2026 at 8:21 PM apache-karaf-dev.pyr3x.com via dev <
> > [email protected]> wrote:
> >
> > > Hi Holger,
> > >
> > > Looks like you guys probably looked at this closer than I did. I would
> > > appreciate any review for the example:
> > >
> > > https://github.com/apache/karaf/pull/3088
> > >
> > > On Thu, Nov 12, 2026 at 08:08:22PM +0100, Holger Friedrich via dev wrote:
> > > > Hi all,
> > > >
> > > > we will use this combination in the next openHAB distribution (Karaf
> > > > 4.5.0-SNAPSHOT, pax-web 11.1.4, osgitech.rest 1.2.3, Jersey 3.1.3, with
> > > > OpenAPI and SSE). The code is still on an unmerged branch. It is known 
> > > > to
> > > > work :-)
> > > >
> > > > We already did some testing, which includes installing and removing 500
> > > > add-ons. So some notes for the new feature set:
> > > >
> > > > * The whiteboard needs a configuration for
> > > > JakartarsServletWhiteboardRuntimeComponent to start (an empty one is
> > > enough,
> > > > the default context path is /), so the feature should ship a default
> > > > <config>.
> > > >
> > > > * With jersey.context.path=/, the default application is a servlet at /*
> > > in
> > > > the default context. In pax-web 11.1.4 it can take over /* from a
> > > servlet in
> > > > another context after unrelated servlet changes (the context ranking is
> > > only
> > > > taken into account when a servlet is registered, not when waiting
> > > servlets
> > > > are re-enabled). A non-root path would also move our REST API, so we
> > > pinned
> > > > the priority instead: service.ranking:Integer=1 on our own servlet, as
> > > the
> > > > servlet ranking is compared first in both places.
> > > >
> > > > * A bundle refresh may end in a cascade that takes down the whole REST
> > > > runtime. We saw this twice: with jakarta.xml.bind-api (two versions
> > > > installed side by side) and with org.jvnet.staxex. jaxb-runtime imports
> > > it
> > > > optionally with DynamicImport-Package: *, so it wires to whatever
> > > stax-ex is
> > > > installed later, and removing that bundle refreshed about 120 bundles.
> > > The
> > > > workaround is to install stax-ex 2.1.0 as a startup bundle together with
> > > > jaxb-runtime. Installed later through a normal feature, it even broke 
> > > > the
> > > > first boot.
> > > >
> > > > Best,
> > > > Holger
> > >
> > >
>

Reply via email to