I personally wanted to look at that PR some time (months)) ago, but
decided to wait a bit and first see what was coming from JAX-RS 2.1
regarding asynch and NIO.
Now that it's clear JAX-RS 2.1 is not going to address anything related
to NIO support, I'll have a look at the PR.
A solution based on HTTPClient 5.0 would be interesting, but I can't say
that's the reason why the PR has been there till now.
Il 14/06/2017 00:50, Steven Schlansker ha scritto:
We're continually running into issues regarding Resteasy's lack of support for
through the JAX-RS client layer.
This seems to be a feature of 2.0 that got implemented by essentially faking it with
I wonder whether Resteasy can truly claim to be a 2.0 compatible implementation given
this serious caveat.
There's a long-open PR: https://github.com/resteasy/Resteasy/pull/540
but it's been stuck since 2014 (!) with little movement.
by this point there's now a competing approach that might upgrade the existing
Apache HTTPClient to 5.0 (nearing release) which accomplishes similar goals
without changing the underlying vendor, and might be easier for the project overall
even if it means this AsyncHttpClient work doesn't get shipped.
What's the status of this? Is this on any roadmap to be implemented any time soon?
I'm surprised it lasted unimplemented this long, this seems like a critical feature
it's part of the spec!
We'd consider contributing a HTTPClient 5.0 PR if that's what is needed to move
but the current situation is untenable for us and if this doesn't get fixed soon we
look for another product that can fulfill our needs.
Thanks for any update you can provide,
resteasy mailing list