ProcessAnnotatedType<? extends BeanManager> never fired?

[ljnelson]

I observe that when I have an observer method in a portable extension that observes ProcessAnnotatedType<? extends BeanManager> the observer method is never called.

I can of course understand why this might have ended up being the case.  Obviously the BeanManager is a very primitive object.

On the other hand, I'm not sure what section of the specification would say this is a special case.

Best,

Laird

[mkouba]

So in this particular case the container is required to fire a PAT for:

1. BeanManager interface found in an explicit bean archive
2. BeanManager implementation found in an explicit bean archive
3. BeanManager implementation found in an implicit bean archive.

See JSR 365: Contexts and Dependency Injection for Java 2.0 .

[ljnelson]

mkouba  wrote:

So in this particular case the container is required to fire a PAT for:

1. BeanManager interface found in an explicit bean archive
2. BeanManager implementation found in an explicit bean archive
3. BeanManager implementation found in an implicit bean archive.

See JSR 365: Contexts and Dependency Injection for Java 2.0 .

OK; the CDI API jar is not an explicit bean archive, and it is the only jar file on my classpath that contains the BeanManager interface.

The only BeanManager implementation is in weld-core and that is not an explicit bean archive, so case 2 does not apply.

weld-core is probably not an implicit bean archive, since it itself is an implementation of CDI, but I'm not going to spend time looking at each and every class in it to see if there is at least one with a bean-defining annotation on it.  If indeed weld-core is not an implicit bean archive, then the fact that I do not observe any ProcessAnnotatedType<? extends BeanManager> event would seem to be correct.  If weld-core is an implicit bean archive, then the fact that I do not observe any ProcessAnnotatedType<? extends BeanManager> would seem to be a bug.

Do I have that correct?

Thanks for your time,

Best,

Laird

[mkouba]

Yes, weld-core is not supposed to be a bean archive. An even if it's included in a shaded jar (Weld SE) the classes are vetoed - see for example core/package-info.java at master · weld/core · GitHub .