Hi Rawand, MessageBodyReader and Writer are used in various contexts. For example, on server side, Reader is used to read request body. On the client side, Reader is used to read response body. Writer

aren't the names MessageBodyReader and MessageBodyWriter confusing enough to let developers think that with MessageBodyReader they can READ both request messages and response messages!!! I would

Hi All, As many of you know, the Java EE community is moving over to the Eclipse Foundation, under the EE4J project. If you are subscribed to this list and want to remain active (or even as a passive

Hi Guys, Nathan has raised Issue #40 [1] with the Concurrency Spec to track this issue. Thanks again for the feedback, Andy [1] https://github.com/javaee/concurrency-ee-spec/issues/40 J.

Good luck. Please keep us informed. -Markus

Hi Markus, Ondro Sorry for the slow reply - was out sick yesterday. I think your proposed plan is a good course of action. Some additional thoughts: MK> Without any changes of the JAX-RS spec

Without any changes of the JAX-RS spec and Concurrency Utils spec JAX-RS will definitively capture the initial context only, so this is what is to be implemented right now. In any doubt please check

I also understand that, according to the current specs, the CompletionStage executes async tasks with the context of the previously finished task and not with the context of the component that calls

Andy, JAX-RS has technically no chance within Java EE 8 / Java SE 8 to enforce what you want. So it maks no sense to write anything like that into a maintenance release of that spec. What we could

Hi Markus, On the surface, I agree. I think that the "fix" should probably go in the Concurrency spec. The fix in this case is an implementation of the CompletionStage interface that is friendly

Hi Markus, Kevin is not subscribed to the JAX-RS mailing list (but if the conversation continues, he said he would be willing to join). He sent this message: Markus, Unfortunately, I don't have

Andy, I need to say that your question does not seem to be particularly related to JAX-RS: The question you ask would be the exact same even if you do not use JAX-RS at all, but simply do

Hi Markus, Thanks for the response. I understand that open sourcing of Java EE to Eclipse has put things in a sort of "limbo", so I'll just try to focus on the technical aspects of this thread.

Andy, as much as I would love to work on JAX-RS 2.1.1, 2.2 or 3.0, actually this is impossible at the moment. The reason is that JAX-RS is to be migrated from Oracle to the Eclipse Foundation. At

Hi Experts, While working on the JAX-RS 2.1 implementation in Liberty, a colleague of mine discovered some inconsistent behavior related to the reactive client's CompletionStage with regard to

RESTEasy 4.0.0.Beta1 comes with JAX-RS 2.1 implementation; read more at https://developer.jboss.org/en/resteasy/blog/2017/11/13/resteasy-400beta1

Thanks Alessio. Do you know already when(+/-)? I.e. are we taking in weeks or months? --David

Yes, there are. For example Apache CXF 3.2.0, which has just been released. RESTEasy is also going to support JAX-RS 2.1 in the very next future. Cheers Alessio

Hi All, Given that JAX-RS 2.1 is now final, I was wondering what are the plans for the other implementaions when it comes to support JAX-RS 2.1? In other words, are there already 2.1 implementaions

Treating CDI enhancements request as the one of the *equal* importance is reasonable. Making it of the major priority is not IMHO... Cheers, Sergey