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 sugge

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 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 executo

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 implementai

Dear experts, it's our pleasure to announce that JAX-RS 2.1 was officially released, see https://www.jcp.org/en/jsr/detail?id=370. Thanks everyone for participating! Feel free to share this

Hey all, I've quick question. The javadocs of Configuration.getClasses() state: Get the immutable set of registered JAX-RS component (such as provider or feature) classes to be instantiated, injected

Pavel, as the spec does not explicitly mention it, can you please confirm that what the spec actually wants to say is that CompletionStage does not only imply async when declared as a method's ret

Hi Pavel When will the final API be published to Maven Central ? 31 July was the finish of the Final Approval Ballot Thanks, Sergey

Last thursday I gave a talk on JAX-RS 2.1 at JFS2017 conference using Jersey 2.26. One question was what the status of the JAX-RS implementations is _besides_ Jersey. Hence I would like to kindly ask

Dear experts, we'd like to announce that Proposed Final Draft was published on JCP JSR 370 page [1]. I'd like to encourage you all to review provided artifacts and let us know if you have any feed

A target of JAX-RS 2.1 is support for Java 8. So I wonder why still idioms of the pre-8 age are used in the API implementation instead of Java 8 idioms. For example: default OutboundSseEvent newEvent

Experts,   I know this is really late to discuss, but in fact, I doubt that it was a good decision to take WriterInterceptor out of the processing chain for SSE events.   In fact, today I set up a

Hey everyone, I've a question regarding JAX-RS and @ValidateOnExecution. Please have a look at the following code:   @GET   @Path("/foobar")   @ValidateOnExecution(type = ExecutableType.NONE)   public

Dear Spec Leads,   the JSR 370 charter says that with JAX-RS 2.1 the JAXB technology should become conditional.   Looking at the last spec draft I cannot find anything about that. Quite contrary i

Hi I created an issue awhile back to get something like @Path(value="/", doc="the path") supported for all of the JAX-RS annotations. The idea is to come up with a single well known property that

Dear experts, we are in a stage when we are re-reading spec document and javadoc (you're welcomed to help us - if you have some favorite typo anywhere in JAX-RS and you wan't to get

Dear experts, Thank you for a productive discussion about CDI integration. We now have a good understanding of what can be achieved when using the new CDI 2.0 API. Our recent analysis has conclude

Dear experts, we originally intended to include compiled module-info to JAX-RS API jar. Original plan was to prepare a release on final or "almost" final Java SE 9 compliant JDK. As you might know

Hi, Time is quickly running out, and I guess what the plans are regarding CDI alignment. There's an open issue [1] labeled as "2.1-candidate" but it seems no work has been done on that yet. Given the

Dear experts, as you might have noticed, we dealt with several small issues in the past couple of weeks. Notable ones: - @Priority for providers - JSON-B integration update - Introduction of JSON-P