AfterTypeDiscovery.addAnnotatedType: should be picked up by bean scanning, yes?

[ljnelson]

I've added a few annotated type instances for a given class, each with a distinct ID using the AfterTypeDiscovery.addAnnotatedType(String, Class) method introduced in CDI 2.0EDR2.

With that configurator, I've programmatically added the Dependent, Default, and Any annotations to the class.  My understanding is that the Dependent annotation on the class coupled with its preexisting @Inject-annotated constructor would constitute a bean defining annotation, and hence this annotated type should be "picked up" by the container during bean discovery as an ordinary managed bean.

In Weld 3.0.0 Alpha17, I do not see a container-discovered bean representing this type when bean discovery is finished.

I was under the impression that types added in this manner would be scanned by the container as though they had existed in this form on disk.

Is there something else I must do?

Thanks,

best,

Laird

[ljnelson]

Hmm; I think there's a bug here.  I have added an annotated type using the addAnnotatedType(String, Class) method, and it does not (a) result in a bean being discovered or (b) the type being available from AfterBeanDiscovery.getAnnotatedType(String, Class).  Nor is a ProcessSyntheticAnnotatedType event fired.  I'll see if I can boil this down into a test case.

[ljnelson]

Filed WELD-2292 with test case.

[ljnelson]

Looks like I duplicated WELD-2242.