Support newer Jetty versions

[wborn]

Jetty 9.4 is EOL so it would be nice if newer Jetty versions are also supported.

There is a whole range of Jetty options nowadays (see the Jetty project page):

Jetty Version	Servlet namespace(s)	Java Version	Pax Web Version	Karaf Version
12.0.x	javax.servlet, jakarta.servlet	17+	10.0.x (WIP)	-
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

Ideally jUPnP would also support Jetty 12 but that also requires Java 17.

The OSGi world is also lagging and haven't made the switch to the Jakarta namespace yet. Pax Web 8 uses Jetty 9.4 and Pax Web 9 supports Jetty 10. Pax Web 10 using Jetty 12 is still WIP, see ops4j/org.ops4j.pax.web#1802. Apache Karaf is still using Pax Web 8.

It might be an idea to split off the Jetty transport into its own module. That way multiple transports for different Jetty versions can be added. Each module can then also properly define its dependencies which would also prevent issues like #157 while still not having any 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.