I find that when I am attempting to reload a handler with pedestal I also need to re-evaluate the service that calls the handler for the changes to take effect. Are there any tips to bypass having to reload the service that calls the handler ?

@jdkealy for development mode, change your routes to (fn [] (expand-routes (deref #'my-routes)) in the service-map (instead of the default, something like: (expand-routes my-routes) )

hey folks: here is my routes and the logs http://paste.debian.net/1149907/

any post request to /q returns 404

am I doing it wrong ?

hello. I am using pedestal and seeing some weird behaviour, when I catch an exception the interceptor chain restarts instead of returning my response

(catch java.util.concurrent.ExecutionException e
                    (log/info :msg "return error")
                    (assoc context :response
                           {:status 408
                            :body {:status "error"
                                   :message (format "Operation Timed out %d seconds" wait-time)}}))

00:58:50.511 [qtp463993419-109] INFO  payment-gateway.routes.collection - {:msg "valid public key ?", :line 20}
00:58:50.525 [qtp463993419-109] INFO  payment-gateway.routes.collection - {:msg "valid referency id ?", :line 40}
00:58:50.621 [qtp463993419-109] INFO  payment-gateway.routes.collection - {:msg "create payment", :line 119}
00:58:52.667 [qtp463993419-109] INFO  payment-gateway.routes.collection - {:status :accepted, :line 122}
00:58:52.667 [qtp463993419-109] INFO  payment-gateway.routes.collection - {:msg "process request", :line 125}
00:59:30.555 [qtp463993419-109] INFO  payment-gateway.routes.collection - {:msg "return error", :line 136}
00:59:30.565 [qtp463993419-110] INFO  payment-gateway.routes.collection - {:msg "valid public key ?", :line 20}
00:59:30.566 [qtp463993419-110] INFO  payment-gateway.routes.collection - {:msg "valid referency id ?", :line 40}