Re: Clarification of Configuration.getClasses() behavior
toggle quoted messageShow quoted text
I would rather say, we have a charter for JAX-RS 2.2 to provide a more concise phrasing in the spec. :-)
From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of Sergey Beryozkin
Sent: Dienstag, 29. August 2017 10:43
Subject: Re: [jaxrs] Clarification of Configuration.getClasses() behavior
I saw a wink there all right, but did not assume it was there to change the meaning of sentence. Perhaps it means I lack a sense of humour :-).
Looks like RestEasy got it right after all :-)
On 28/08/17 18:35, Markus KARG wrote:
seems you missed the irony smiley at the end of my posting.
Putting aside the fact RI is obviously of high quality, the following may shock you but: RI may also have bugs, some of them related to the interpretation of the spec/API...
On 27/08/17 10:37, Markus KARG wrote:
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. ;-)
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 and utilized in the scope of the configurable instance. For each component type, there can be only a single class-based or instance-based registration present in the configuration context at any given time.
My question is whether the returned set of classes is supposed to contain resource classes or not.
I'm asking this because Jersey seems to return resources but RESTEasy doesn't.
PS: Congratulations for delivering JAX-RS 2.1!
Join email@example.com to automatically receive all group messages.