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

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

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

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

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

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

That's a good point, and certainly not something we can easily resolve. As others have mentioned, a strength of Java EE is integration with other specs like CDI, JSON-B, etc. But let us not forget

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

Dear experts, Thank you for a productive discussion about CDI integration. We now have a good understanding of what can be achieved when using the new CDI 2.0 API. Our recent analysis has concluded

Turning on CDI by default implies that all methods have to be non-final, which is not backwards compatible to JAX-RS 2.0. So we cannot do that. -Markus

I created an new issue to turn the @Path annotation into a CDI stereotype if used in a CDI container: https://github.com/jax-rs/api/issues/556

Regarding the dependency on CDI, I don't think that JAX-RS must depend on CDI at runtime at this stage. However, it could at least depend on @Inject from JSR 330 which should be preferred to @Context

Even it wouldn't be a problem, if @Path annotation isn't a bean defining annotation, the event wouldn't be fired at all in the "annotated" discovery mode if there are no other CDI beans (possible if

Hi Pavel, 2017-06-05 11:07 GMT+02:00 Pavel Bucek <pavel.bucek@...>: The fallback mechanism of the JDK ResourceBundle API will kick in which depends on the relationship between requested

Hi Pavel, thank you for adding this. I filed the OCA yesterday so next time you should be able to accept my contributions. Regards Dennis

oops. :) will be fixed in the next milestone. Thanks, Pavel

Hey Pavel, thanks a lot. It is great to finally see this feature in the spec. Just one minor typo: "withing" should be "within".

please seehttps://github.com/jax-rs/api/commit/d18207327468870ab885120c3790e36a741af26d

Hi Gunnar, I'm sorry to say that, but I don't think that proposal is viable. What if the app (BV layer) knows Locales L1 and L2 and the user (request) asks for L3;q=0.9, L2;q=0.5, L1;q=0.1. In the

Hi Pavel, Any chance for considering the latest proposal for passing the (highest-quality) request locale to Bean Validation? Thanks, --Gunnar 2017-06-02 14:48 GMT+02:00 Pavel Bucek