Please seehttps://github.com/jax-rs/api/commit/f84db6dbb13801411560368deaac7d0d5004db65 Manifest entry "Automatic-Module-Name" was added (based

Hi Guillermo, I really appreciate your activity around this area, but at this point, I don't think we should consider pursuing any change. We are days from Proposed Final Draft and we

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 rid

Sounds reasonable. If other vendors agree to support this feature, we should add it to the spec.

Hi Pavel, I understand it. We (the community) should have raised this before. I just hope we have this issue as high priority for the next version. Thanks for your efforts! Regards Guillermo González

Hi, It's indeed a tad too late if the Proposed Final Draft is only days away. Perhaps in the meantime individual application servers can do a little bit more to integrate with CDI out of the box, like

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

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

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 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 As far as I understand that is what the idea behind ResourceContext.getResource(Class<T>) was ? Thanks, Sergey

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 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 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 Pavel You are right, makes sense Sergey

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

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

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

+1 — Santiago