pedestal 2025-11-14

Feedback about my attempt that failed to upgrade from pedestal 0.7 to 0.8 - jetty 1. it cant print the (scope captured) ctx - it throws an exception because :servlet-response throws during toString 2. can't access the "server" object after start About 1: It's very annoying. All my inspection tools end up breaking. not sure how to handle that. About 2: I'd like to be able to start the server with port 0 and afterwards, inspect which port is being used. Would it be possible to add a new method server-port to PedestalConnector ? It can be optional and throw an exception if not implemented (or return nil by default - not sure).

Just ran into this myself. Doing this as a workaround:

(defmethod print-method org.eclipse.jetty.ee10.servlet.ServletApiResponse
  [_ ^java.io.Writer w]
  (.write w "#<ServletApiResponse>"))
Not sure what the path forward here is, but I agree; very annoying.

Just to be clear. I understand this is a Jetty 12 decision, not blaming the fine folks maintaining pedestal. Still, I think this has to be addressed in pedestal to avoid a lot of noise.

👍 1