For OSGi you must (as in not optional) include a java ServiceLoader provider for your OSGi environment.
The most common is Apache SpiFly. This is the most common reason for various things in Jetty not working in OSGi. (typically it's one of the following the ALPNProcessors, WebSocket, Precomputed Headers Impls, WebApp Configurations) Joakim Erdfelt / [email protected] On Fri, Dec 29, 2023 at 11:46 AM Silvio Bierman via jetty-users < [email protected]> wrote: > I have Jetty 12.0.5 embedded inside an OSGi bundle with all dependencies > embedded. Jetty starts normally and I can get it working with a HTTP > listener. But when I add the code to add HTTPS support I get an error at > startup: > > java.lang.IllegalStateException: No Server ALPNProcessors! > > The jetty-alpn-server and jetty-alpn-java-server artifacts are included > in the bundle JAR as embedded dependency but the ALPN processor still > can not be found, probably because the OSGi class loader is incompatible > with how the search for ALPN processors works. > > Does anyone know how I can resolve this? > > Cheers, > > Silvio > > _______________________________________________ > jetty-users mailing list > [email protected] > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/jetty-users >
_______________________________________________ jetty-users mailing list [email protected] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users
