Re: [cdi-dev] Feature Request

[Matej Novotny <manovotn@xxxxxxxxxx>]

Hello,

this is an interesting idea although it does have some pitfalls in terms of method variants we'd need as well as inability to guard for unsatisfied/ambiguous exceptions.

Last but not least, resolving dependent beans this way would rid users of the ability to destroy them (unless, ofc, we also add a destroy method but then we are re-creating already existing API) potentially increasing the risk of memory leak.

Either way, please capture the idea as a GH issue so that we don't lose track of it - https://github.com/jakartaee/cdi/issues

Regards

Matej

On Thu, Jun 2, 2022 at 2:14 PM Can Türker <tuerker@xxxxxxxxxxxx> wrote:

Dear all,

would be great to have a shortcut for CDI.current().select(xxx.class).get().

My proposal would be: CDI.get(xxx.class).

Thanks for consideration.

Best regards,

Can

-- 
-----------------------------------------------------------------------
Dr.-Ing. Can Türker                                tuerker@xxxxxxxxxxxx
Functional Genomics Center Zurich                  phone +41 44 6353900
UZH / ETH Zurich                                   fax   +41 44 6353922
Winterthurerstrasse 190, Irchel Y32 H04
CH-8057 Zurich        http://www.fgcz.ch/the-center/people/tuerker.html
----------------------------------------------------------------------- 

_______________________________________________
cdi-dev mailing list
cdi-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdi-dev