Markus, your description of user definitely doesn't read the spec document, javadocs, etc. So what exactly would be achieved by putting a note into the spec document? My

Pavel, this complete Jigsaw topic is a mess for the end user and I wonder what the OpenJDK guys wanted to reach with making JAXB optional… In reality no end user knows anything about Jigsaw (end

Well.. the spec says nothing about running on Java 9, since Java 9 won't be final when JAX-RS 2.1 is released. When a user want's to run on Java 9, it is expected that he knows what

Pavel, my point is that the application *user* simply does not know that he must use --add-module when running any binary application on Java 9, as the *user* has no knowledge that JAXB is used

that depends on how the application is ran (on Java 9). If the app is on classpath, the *user* has to --add-module java.xml.bind. Nobody can do that for him. If the app is on module

I do not say we should remove JAXB, I just wanted to ask because it was in the JSR 370 charter. I also do not see a big benefit of removing JAXB. The only problem I see is running JAX-RS 2.1 on Java

+1 — Santiago

I see no practical point in doing it anyway. It's unlikely that any of the existing JAX-RS implementations will choose to annoy some of its users and just do not ship JAXB-aware

Hi Markus, we learned that it is not possible to do that in this release. The main issue is that we cannot just deprecate something, there is a strict policy related to making backwards

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

Hi Pavel I agree (2nd time in a row :-)) Cheers, Sergey

Hi Pavel You are right, makes sense Sergey

Hi Sergey, I believe that javadoc is the right place for documentation like this. Not to mention that writing the documentation to the annotation string literal is not very convenient, especially

Hi Sergey, that's true, but does that contradict what we did? (I do see that as a shortcut, which makes sense to have, nothing more). Regards, Pavel

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

Hi Pavel As far as I understand that is what the idea behind ResourceContext.getResource(Class<T>) was ? Thanks, Sergey

Hi Sebastian, that's easy to write in the spec, the consequences are not so simple to consider and implement. Most of the CDI changes won't be in the API at all - its not about the

Hi Pavel, Totally understandable. However, let me raise an issue that is related to the CDI topic -- I think the whole CDI integration contains several, different concerns at once:

Hi, Not at the moment, but pieces of work for it have been done (PRs pending) and I hope to be able to work on that ASAP, so should be sooner rather than later. Kind regards, Arjan Tijms

Is the Payara nightly build already able to execute JAX-RS 2.1 applications?