+1. For Java EE users, it's a really needed feature of equal importance. Regards, Guillermo González de Agüero

Congratulations and thanks Pavel, Santiago and everyone involved on this release! Now that the spec is complete, any plans to move the JAX-RS repositories under the Java EE organization? Regards, Guil

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, I invited Antoine Sabot Durand (CDI Spec lead) to join the conversation and he replied me today that he and the Weld team will have a look at the issue as they have already been helping other spec

Hi, As far as I understand, the module dependency Pavel talked about would just mean that the CDI API would be required to be there, not that it'd require a CDI implementation to work. It wouldn't bre

Hi, I've checked it and adding a new bean with CDI 2.0 is just as simple as creating an extension like this (taken from http://www.next-presso.com/2017/02/nobody-expects-the-cdi-portable-extensions/):

Hi again, It might me possible to register the resources to CDI with the BeforeBeanDiscovery#addAnnotatedType() method [1], provided that the JAX-RS runtime knows its resources by the time CDI fires t

Hi Pavel, First, thanks for taking the time to consider this. Arjan has summarized the idea. With this option, JAX-RS implementations themselves will stay the same as today. Taking Jersey as an exampl

Hi Pavel, It's not currently doable right now with the standard APIs. My original proposal was to require the application server to do it in a vendor specific manner. WildFly already does it that way

Hi, I agree @Context annotation must still work, at least from the time being. But I see two things here: - It's easy to handle injection of @Context via CDI with just a custom extension. The spec can

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

Hi, I was writing to propose exactly that. That's be the more flexible approach, and would resolve my open question about what exactly is a built-in provider (https://github.com/jax-rs/api/issues/537#

Hi, Have you considered how this will behave when the provider is a CDI @Alternative or @Stereotype? I'm unsure how much those could interfere but I think it's something to take into account nonethele

Hi, Perhaps this is a naive question, but how is the "managed" executor service handled on the Web Profile? Does "managed" mean that it must use a JSR 236 executor, or does it just refer to any "conta