pedestal 2023-06-26 | Slack Archive

hlship21:06:36

Leading into Pedestal 0.7.x, a big focus will be to bring Jetty to version 10 or 11 and to add features to make it easier to enable web sockets and listening on multiple hosts and ports; this should be easy enough for Jetty and maybe Tomcat, but Immutant hasn't been updated in 6 years and does not appear to be widely used. In the interests of keeping our work load approachable, I'd like to float the idea of removing the pedestal.immutant library so that we can focus of Jetty and Tomcat. I've always been a fan of only shipping code that has been tested in a running application. As much as I love tests and testing, there's no substitute for hands on "using it in anger". That's never been a problem for Tapestry (in the distant past), Pretty, Lacinia, and pedestal.jetty. Unfortunately, I have never used the pedestal.tomcat library - all my previous experience as a Pedestal user focused on Jetty. Are there people in the Pedestal community using Tomcat, and if so, are there any volunteers to help us validate that Pedestal 0.7.0, which may also switch to a more recent version of Tomcat, is fully operational in Tomcat?

👍 16

Eugen10:06:43

I would like to point out that Jetty 10 and 11 are different things. Jetty 11 uses the new jakarta.servlet namespage for Java EE (Servlet API). Jetty 10 uses the old javax.servlet api for apps that have not been migrated yet (the majority I would imagine)

Eugen10:06:07

I would argue that both should be supported.

👍 2

Eugen10:06:25

Jetty 10 being the last release to support javax.servlet

hlship17:06:38

The major impact is the Java class io.pedestal.servlet.ClojureVarServlet - it's where the majority of the javax. imports occur; this implies that we will need to update Tomcat at the same time as Jetty. Jetty 11 and Tomcat 10.0 both use jakara. namespaces. Jetty 10 would be easier, but it hits end-of-life in only a year.

PK Anane15:07:52

#Also sent to the channel

I see.. what will be the impact of supporting only Jetty 11? Maybe if a sensitization drive is begun the community will be aware of what to expect. Especially since Jetty 10 hits EOL

PK Anane15:07:52

replied to a thread:Leading into Pedestal 0.7.x, a big focus will be to bring Jetty to version 10 or 11 and to add features to make it easier to enable web sockets and listening on multiple hosts and ports; this should be easy enough for Jetty and maybe Tomcat, but Immutant hasn't been updated in 6 years and does not appear to be widely used. In the interests of keeping our work load approachable, I'd like to float the idea of removing the pedestal.immutant library so that we can focus of Jetty and Tomcat. I've always been a fan of only shipping code that has been tested in a running application. As much as I love tests and testing, there's no substitute for hands on "using it in anger". That's never been a problem for Tapestry (in the distant past), Pretty, Lacinia, and pedestal.jetty. Unfortunately, I have never used the pedestal.tomcat library - all my previous experience as a Pedestal _user_ focused on Jetty. Are there people in the Pedestal community using Tomcat, and if so, are there any volunteers to help us validate that Pedestal 0.7.0, which may also switch to a more recent version of Tomcat, is fully operational in Tomcat?

I see.. what will be the impact of supporting only Jetty 11? Maybe if a sensitization drive is begun the community will be aware of what to expect. Especially since Jetty 10 hits EOL

2023-06-26

Channels