Good luck. Please keep us informed. -Markus

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 t

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 do

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 CompletionSt

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 the

I would rather say, we have a charter for JAX-RS 2.2 to provide a more concise phrasing in the spec. :-) -Markus

Yes automatic discovery is to be considered for Configuration.get*, so it returns more than Application.getClasses.

IIRC… * Application.getClasses() is implemented by the application developer to let the JAX-RS engine know which components (= resources and providers) are to be loaded. It exists since JAX-RS 2.0 and

Sergey, seems you missed the irony smiley at the end of my posting. -Markus

Due to the fact that Jersey is the RI and RESTEasy is not, what Jersey does is inherently correct, and what RESTEasy does is not. ;-) -Markus

Will you keep us updated on IBM's implementation progress? :-) -Markus

Congratulations! When do we start with JAX-RS 2.2? ;-)

I think it make sense to file this as an issue for JAX-RS 2.2 / 3.0, so a future specification will align CXF and Jersey and give application developers safety how things shall work.

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 return

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

Ok I agree that we should not touch old APIs, but we should add @throws to new APIs like Sse and SseEventSink then. Also I am not convinced that IAE is only for application callers: Why should it stay

Lol ;-D Pavel, I meant the SSE API, actually, but right, I did not check ALL APIs. So to make your claim a valid argument, we should now add @throws IllegalArgumentExcpetion to the JavaDocs of ALL pla

Pavel, actually looking at the rest of the *API* (as you suggested) I did not find declaration of IAE, as it is solely part of the *implementation* -- it is rather undocumented that in particular IAE

So it is by intention that you still use IllegalArgumentException instead of NPE. Understood. :-)

Pavel, from the view of an application programmer the arguments look quite different: SSE within JAX-RS is not recognized as a different technology, but simply as a push-add-on that will keep the clie