Re: [weld-dev] [jsr-299-eg] Updated spec with @BeanTypes and clarification of @New

But that's the issue, because it triggers scanning of all application classes.

On top of that, it's speculative scanning. If the bean isn't discovered until we find a use of the "second bean" (with @New), should we tentatively retain as valid all the resources the bean declares, during scanning, only to discard them if it turns out the bean does not actually exist (i.e. there is no usage with @New)? I'm also starting to wonder where this process ends, given that the SPI lets the application register new beans at runtime. Does that mean that all resources declared anywhere are valid?