[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jetty-users] Question about ALPN when embedding Jetty inside an OSGi bundle
|
Thank you Joakim,
I looked into SpiFly and it seems quite complex. It sounds to me
like it is targeted at crossing bundle boundaries through
ServiceLoaders while all I want is for Jetty (which is an internal
implementation detail of my bundle) to use its own ALPN
implemenation. Nothing ServiceLoader, ALPN or even Jetty/Servlet
should be visible outside the bundle. I am not doing HTTP whiteboard
at the OSGI level and do not want to deploy Jetty as OSGI bundle(s).
If I could hardwire my embedded Jetty to its ALPNProvider and
forsake ServiceLoader altogether that would be my prefered solution.
Is that in any way possible?
Cheers, Silvio
On 30-12-2023 01:59, Joakim Erdfelt
wrote:
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)
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
jetty-users@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users
