Support newer Jetty versions

[wborn]

Jetty 9.4, 10 and 11 are EOL, so it would be useful for jUPnP to support a currently maintained Jetty version.

There is a range of Jetty options nowadays. Jetty 12 supports multiple EE environments and can therefore be used with both the legacy javax.servlet namespace and the newer jakarta.servlet namespace.

Jetty version	Servlet namespace(s)	Java version	Pax Web version	Karaf version
12.1.x	javax.servlet or jakarta.servlet	17+	10.1.x (javax), 11.1.x (jakarta)	4.5.x WIP
12.0.x	javax.servlet or jakarta.servlet	17+	10.0.x (javax), 11.0.x (jakarta)	-
11.0.x	jakarta.servlet	11+	-	-
10.0.x	javax.servlet	11+	9.0.x	-
9.4.x	javax.servlet	8+	8.0.x	4.4.x

The current jUPnP implementation still targets Java 11 and uses Jetty 9.4 with Servlet API 3.1.

The OSGi ecosystem has progressed since this issue was opened:

• Pax Web 10 has been released and provides Jetty 12 support while retaining the javax.servlet namespace.
• Pax Web 11 provides the corresponding Jetty 12 implementation using the jakarta.servlet namespace.
• The Pax Web Jakarta EE 10 work item has been completed.
• The latest released Apache Karaf 4.4.x line still uses Pax Web 8, Jetty 9.4 and javax.servlet. Karaf 4.4.11 uses Pax Web 8.0.35 and Jetty 9.4.58.
• Karaf 4.5 is currently under development as 4.5.0-SNAPSHOT. It is moving directly to Pax Web 11.1.x, Jetty 12.1 and Jakarta Servlet API 6.1.

The current Karaf migration path therefore looks approximately like this:

Karaf 4.4.x
  Java 11+
  Pax Web 8
  Jetty 9.4
  javax.servlet

Karaf 4.5.x (work in progress)
  Java 17+ or possibly Java 21+
  Pax Web 11.1.x
  Jetty 12.1
  jakarta.servlet

The final minimum Java version for Karaf 4.5 does not appear to be settled yet. Jetty 12.1 requires at least Java 17, while there is also ongoing work proposing Java 21 as the Karaf 4.5 baseline.

Karaf is therefore effectively skipping Pax Web 10 and moving directly from Pax Web 8 with javax.servlet to Pax Web 11 with jakarta.servlet.

This means that simply upgrading the existing Jetty dependencies would not provide compatibility with both Karaf generations. Supporting current and future Karaf versions would also require supporting both Servlet namespaces.

It might therefore be useful to split the Jetty transport into separate modules, for example:

• a Java 11 / Jetty 9.4 / javax.servlet transport compatible with Karaf 4.4;
• a Java 17+ / Jetty 12 / jakarta.servlet transport compatible with the future Karaf 4.5 stack;
• optionally, a Java 17+ / Jetty 12 / javax.servlet transport for Pax Web 10 and non-Karaf users.

Each module could then properly define its version-specific dependencies. This would also prevent issues such as #157 and #288 while continuing to avoid implementation dependencies in the Core module.

[kaikreuzer]

It's a pity that the OSGi world is lagging behind so much and Karaf specifically. 😲
I am not so sure, though, how many jUPnP users there are that are using Jetty and no OSGi; I haven't really seen requests for newer versions, so while the idea of multiple transports might be nice, the effort might not be worth it.

I wonder if the non-OSGi way of using jUPnP shouldn't rather be the Java HttpClient, which came with Java 11. This would imho be the most natural way to do HTTP, don't you think?

[wborn]

Using the Java HttpClient may certainly be an option now that the code can use Java 11. However there are also a few Servlets being used. It doesn't look like the Simple Web Server introduced in Java 18 supports Servlets.

It is also possible to use a different Jetty version or some other implementation by using your own UpnpServiceConfiguration implementation.

[kaikreuzer]

Ok, you're right. Then I would assume that we stick to Jetty 9.4.x for now for the 3.0.0 release, right?
We can leave this issue open for anybody to comment, if there is interest in support for newer Jetty versions. If not, we will simply keep it in sync what is supported by Karaf.

[wborn]

Then I would assume that we stick to Jetty 9.4.x for now for the 3.0.0 release, right?

Yes let's stick with it for now.

[peerless2012]

Android 5.0 need java8, so it will be sad if upgrade the jetty version.

[tentechtop]

Could you provide a use case? For example, if my port is 8800, how can I use this project to make my port accessible from the outside network?

[Frontrider]

I can't even attempt to collect the dependencies this library needs. Jetty 9.2.x that I'm seeing in a comment is not on maven central, it starts with 9.3.x.

org.jupnp.transport.impl.jetty.JettyStreamClientImpl can't be initialized because org.eclipse.jetty.http.HttpFields got changed to an interface between those versions.

[joakime]

Be aware of announced changes to Jetty EOL versions

• EOL (End of Life) for Eclipse Jetty 9, 10, 11 and CometD 5, 6, 7 - Update (Oct, 2025) jetty/jetty.project#13984

[Dacesilian]

I would like to vote for upgrading to newer version to use Jakarta Servlet. It's not good to use EOL versions.