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:

For developers it would be very helpful to @Inject JAX-RS managed objects -- mainly UriInfo -- into other (CDI) managed beans. We stumbled across this several times and I think it is an easy thing to require in the spec, something like: If the container supports JAX-RS and CDI/JSR 330, then UriInfo (maybe among others) must be injectable with an appropriate scope (here request scoped I guess). Wouldn't involve any other changes in the API.

WDYT?

Cheers,
Sebastian
   

On 06/08/2017 12:21 AM, Pavel Bucek wrote:

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 still don't have ready everything we HAVE TO deliver. Adding any other (non-trivial) changes like this is like sawing off the branch we’re sitting on..

Thanks and regards,
Pavel

On 06/06/2017 18:38, Guillermo González de Agüero wrote:

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 integrate with CDI.

CDI 2.0 is already final but maybe they have some ideas that could help here going some step foward. I ask you and Santiago and the rest of the EG please to wait a little for them to comment here before taking a definitive decission.

Regards,

Guillermo González de Agüero

On Tue, Jun 6, 2017 at 5:47 PM, Pavel Bucek <pavel.bucek@...> wrote:

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 that providing a better CDI integration would require more experimentation than what we can do in this minor release. We also don't want to introduce "hard" dependency on CDI API to the JAX-RS API as many JAX-RS developers rely on running JAX-RS outside of CDI context.

We agree that CDI can be used as the "glue" of the whole Java EE platform and JAX-RS can do more in terms of the CDI integration when running in a Java EE container. Currently, such enhancements are NOT forbidden at the spec level and JAX-RS providers are free to introduce support that goes beyond what JAX-RS spec mandates. Further experiment in this area can help to gather more feedback for any future re-evaluation of improved CDI/JAX-RS integration story. Also, this feedback may help CDI owners to provide public API enhancements to enable full JAX-RS /CDI integration in a portable way.

Thanks again for the discussion on the mailing list.

Best regards,
Pavel & Santiago