dude-abides

Bottom line is that you can take a Java object, serialize it to JSON, read the JSON back in and compare the root JsonNode of the Java Object and the...

I just tried with 3.1.6 and 3.0.13, and timeouts are not respected.

For the timeout issue I was setting connect timeout and read timeout to 60s. I pointed the client at a remote (not localhost) server that was not running. It never...

I will attempt to reproduce when I get a chance.

Step to recreate 1. Run a server and client on the same machine 2. Make one request to server successfully 3. Shutdown the server (forced) 4. Make another request to...

Why is there no comment in "5.5 Client Transport Connectors" discussing PATCH support in the default provider. It is not supported past Java 16. I have tried JdkConnectorProvider and Apache5ConnectorProvider...

> @dude-abides I'd recommend using NettyConnector, which is the most advanced connector (besides the default HttpUrlConnector) we support. Another option is to try the HelidonConnector (also based on Netty) backed...

@jansupol You suggested Helidon and Netty. Netty does not respect timeouts. If I take my server down after making a request to the server. The next request hangs endlessly. You...

Created new issue to better capture my situation: https://github.com/eclipse-ee4j/jersey/issues/5598

> Adding `--add-opens java.base/java.net=ALL-UNNAMED` to the client application allows for using the HTTP Patch with the HttpUrlConnector and HTTP requests. Additional `--add-opens java.base/sun.net.www.protocol.https=ALL-UNNAMED` to the client application allows for using...