[73cat] autodiscover what can be injected with CDI

[Viggo Navarsete]

Hi,

does anyone have comments to my issue about adding a feature to Netbeans for "autodiscover"/list all possible things that could be injected using @Inject by scanning what can be produced by @produces in CDI? I feel that if CDI is "over-used" it can be hard (for both newbies and experienced CDI users) to figure out what is going on...http://netbeans.org/bugzilla/show_bug.cgi?id=220693..is it only me, or is this something that could add value to netbeans?

Regards,

Viggo

[Michael Nascimento]

Not only things from @Produces can be injected, so maybe something
like this with a see all? CDI extensions would have to be manually
handled though, i.e., NetBeans would have to provide a SPI for
extension developers to code an implementation for their own
extension.

Regards,
Michael

On Wed, Oct 24, 2012 at 1:51 AM, Viggo Navarsete
<[hidden email]> wrote:

> Hi,
>
> does anyone have comments to my issue about adding a feature to Netbeans for
> "autodiscover"/list all possible things that could be injected using @Inject
> by scanning what can be produced by @produces in CDI? I feel that if CDI is
> "over-used" it can be hard (for both newbies and experienced CDI users) to
> figure out what is going
> on...http://netbeans.org/bugzilla/show_bug.cgi?id=220693..is it only me, or
> is this something that could add value to netbeans?
>
> Regards,
> Viggo

[Viggo Navarsete]

I think such a feature belong to either the Navigate or Edit (with a new "Find CDI beans" feature) menu, or maybe by right-clicking on a field being annotated with @Inject and Netbeans can give a list of possible things that could be injected (I assume this would be the "black magic" to be implemented;) ).

I foresee the usage of CDI to maybe become the same issue as people have with interceptors..they don't see where things are applied...or as with using Spring when declared in XML files...don't see directly in code where  the link to other files are. I hope Netbeans can be proactive here and give the user some help before CDI become painful and hard :)

On Wed, Oct 24, 2012 at 6:54 AM, Michael Nascimento <[hidden email]> wrote:

Not only things from @Produces can be injected, so maybe something
like this with a see all? CDI extensions would have to be manually
handled though, i.e., NetBeans would have to provide a SPI for
extension developers to code an implementation for their own
extension.

Regards,
Michael

On Wed, Oct 24, 2012 at 1:51 AM, Viggo Navarsete
<[hidden email]> wrote:
> Hi,
>
> does anyone have comments to my issue about adding a feature to Netbeans for
> "autodiscover"/list all possible things that could be injected using @Inject
> by scanning what can be produced by @produces in CDI? I feel that if CDI is
> "over-used" it can be hard (for both newbies and experienced CDI users) to
> figure out what is going
> on...http://netbeans.org/bugzilla/show_bug.cgi?id=220693..is it only me, or
> is this something that could add value to netbeans?
>
> Regards,
> Viggo

[Benno Markiewicz]

Does the feature "Inspect injectables" helps you?
http://wiki.netbeans.org/NewAndNoteworthy69m1#Contexts_and_Dependency_Injection

Greetings, markiewb

Am 24.10.2012 07:10 schrieb "Viggo Navarsete" <[hidden email]>:

I think such a feature belong to either the Navigate or Edit (with a new "Find CDI beans" feature) menu, or maybe by right-clicking on a field being annotated with @Inject and Netbeans can give a list of possible things that could be injected (I assume this would be the "black magic" to be implemented;) ).

I foresee the usage of CDI to maybe become the same issue as people have with interceptors..they don't see where things are applied...or as with using Spring when declared in XML files...don't see directly in code where  the link to other files are. I hope Netbeans can be proactive here and give the user some help before CDI become painful and hard :)

On Wed, Oct 24, 2012 at 6:54 AM, Michael Nascimento <[hidden email]> wrote:

Not only things from @Produces can be injected, so maybe something
like this with a see all? CDI extensions would have to be manually
handled though, i.e., NetBeans would have to provide a SPI for
extension developers to code an implementation for their own
extension.

Regards,
Michael

On Wed, Oct 24, 2012 at 1:51 AM, Viggo Navarsete
<[hidden email]> wrote:
> Hi,
>
> does anyone have comments to my issue about adding a feature to Netbeans for
> "autodiscover"/list all possible things that could be injected using @Inject
> by scanning what can be produced by @produces in CDI? I feel that if CDI is
> "over-used" it can be hard (for both newbies and experienced CDI users) to
> figure out what is going
> on...http://netbeans.org/bugzilla/show_bug.cgi?id=220693..is it only me, or
> is this something that could add value to netbeans?
>
> Regards,
> Viggo