The https://jcp.org/en/jsr/detail?id=370 page has to be updated with proper links to discussion mailing lists, archives etc; can the EG lead please do that?

Hi Jim,  We’ll have to wait until the e-mail migration is completed to look at the original thread.  I can’t recall if this particular pattern was explored. Generally, however, a provider in JAX-RS is

Dear experts, please let me know if you find anything wrong with following statements: on Java EE container: - JAX-RS client will use ManagedExecutorService for async/reactive calls unless set exp

Dear experts, as we already stated, we'd like to support returning CompletionStage from the resource mehod, corresponding spec issue is here: https://github.com/jax-rs/api/issues/551 The only open

Hi all,   It might be too late to add this (if so, no worries), but I've been running into a few customer situations where customers are using HTTP/HTTPS proxy servers with their JAX-RS client APIs.

Dear experts, there is couple of filed issues related to provider ordering, namely: https://github.com/jax-rs/api/issues/538 https://github.com/jax-rs/api/issues/537 We

Dear experts, we'd like to make the HTTP PATCH support on the client optional, throwing UnsupportedOperationException on client runtimes, which don't support that method. I know that we already ha

Dear experts, we are working on improving integration with BeanValidation [1], and seems like if we choose to address this issue, the change will be slightly bigger than I anticipate

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

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

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

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

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

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

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

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

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